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.

Sign up for GitHub

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

Jump to bottom

[api/status] Add telemetry to track usage of v8format flag #112519

Closed
lukeelmers opened this issue Sep 18, 2021 · 2 comments
Closed

[api/status] Add telemetry to track usage of v8format flag #112519

lukeelmers opened this issue Sep 18, 2021 · 2 comments
Labels
chore 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 Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@lukeelmers
Copy link
Member

In #110830, we set the default response format of /api/status to be the v8format, and introduced a new v7format flag for folks who want to get the legacy behavior. At that time, we also added telemetry to track usage of v7format so we can eventually phase it out.

However, we did not add telemetry to track usage of the v8format flag. While it costs very little from a maintenance perspective to keep this flag around, it might be nice to understand how widely it is being used in case we want that info when we are looking to remove it.
@lukeelmers lukeelmers added chore Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc loe:small Small Level of Effort impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Sep 18, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@lukeelmers lukeelmers mentioned this issue Sep 18, 2021
Closed
@pgayvallet
Copy link
Contributor

it would be too late to add this telemetry today to potentially remove this v8format flag for 9.0, so given there is virtually no maintenance cost for us to keep this flag, I'll go ahead and close this issue.

@pgayvallet pgayvallet closed this as not planned Won't fix, can't repro, duplicate, stale Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore 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 Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pgayvallet @lukeelmers @elasticmachine