Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Reporting] Add telemetry for deprecated export type usage #105868

Closed
tsullivan opened this issue Jul 15, 2021 · 6 comments · Fixed by #108614
Closed

[Reporting] Add telemetry for deprecated export type usage #105868

tsullivan opened this issue Jul 15, 2021 · 6 comments · Fixed by #108614
Labels
impact:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:large Large Level of Effort v8.0.0

Comments

@tsullivan
Copy link
Member

tsullivan commented Jul 15, 2021

Following adding support of 6.2 PDF job POST URLs in 8.0, #108271, there needs to be telemetry data collected on the extent of usage of deprecated export types.

@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 15, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jul 15, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Jul 19, 2021
@stacey-gammon
Copy link
Contributor

Do we have telemetry that lets us know how often these legacy-style URLs are being used?

@tsullivan
Copy link
Member Author

@stacey-gammon

Do we have telemetry that lets us know how often these legacy-style URLs are being used?

Not at the moment. The telemetry metrics tell us how often each type of export is used, butprintable_pdf export type has this compatibility override making it support both the old-style job params and new-style.

I added this issue to add metadata in the compatibility layer and add it to telemetry, so we can count how often the old-style job params are still being used: #108118

@exalate-issue-sync exalate-issue-sync bot changed the title [Reporting] Add a deprecation to the compatibility layer for 6.2 URLs in PDF job params [Reporting] Add telemetry to the compatibility layer for 6.2 URLs in PDF job params Aug 11, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. impact:critical This issue should be addressed immediately due to a critical level of impact on the product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels Aug 11, 2021
@tsullivan tsullivan changed the title [Reporting] Add telemetry to the compatibility layer for 6.2 URLs in PDF job params [Reporting] Add telemetry for deprecated export type usage Aug 13, 2021
@tsullivan
Copy link
Member Author

@stacey-gammon I've updated the issue title and description

@stacey-gammon
Copy link
Contributor

Thanks @tsullivan! I think that means we can remove the breaking change label now?

@exalate-issue-sync exalate-issue-sync bot added loe:large Large Level of Effort and removed loe:small Small Level of Effort labels Aug 18, 2021
@tsullivan
Copy link
Member Author

Closed via #108118

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:large Large Level of Effort v8.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants