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] Legacy CSV export type can be removed #121259

Closed
tsullivan opened this issue Dec 15, 2021 · 1 comment · Fixed by #121435
Closed

[Reporting] Legacy CSV export type can be removed #121259

tsullivan opened this issue Dec 15, 2021 · 1 comment · Fixed by #121435
Labels
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 technical debt Improvement of the software architecture and operational architecture

Comments

@tsullivan
Copy link
Member

Kibana version: 8.1

Fewer than 1% of all clusters reporting telemetry are using the legacy implementation for CSV export in versions where the replacement version is available. This means that the legacy export type under x-pack/plugins/reporting/server/export_types/csv can be removed.

@tsullivan tsullivan added technical debt Improvement of the software architecture and operational architecture Team:AppServicesUx labels Dec 15, 2021
@elasticmachine
Copy link
Contributor

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

@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Dec 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. and removed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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 technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants