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

[Meta][Telemetry] Reduce telemetry footprint #119466

Closed
14 of 19 tasks
Bamieh opened this issue Nov 23, 2021 · 6 comments
Closed
14 of 19 tasks

[Meta][Telemetry] Reduce telemetry footprint #119466

Bamieh opened this issue Nov 23, 2021 · 6 comments
Labels
Feature:Telemetry impact:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:large Large Level of Effort Meta Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@Bamieh
Copy link
Member

Bamieh commented Nov 23, 2021

Reducing the telemetry footprint ensures future scalability of our telemetry and puts a system in place to enable performance optimizations for our collection methods. This also helps reduce the number of people opting out of telemetry in cases where telemetry is causing significant spikes in resources.

@Bamieh Bamieh added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Meta Feature:Telemetry labels Nov 23, 2021
@elasticmachine
Copy link
Contributor

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

@rudolf
Copy link
Contributor

rudolf commented Nov 23, 2021

There's some overlap in this issue and #117489

@Bamieh
Copy link
Member Author

Bamieh commented Nov 23, 2021

@rudolf ++. I've consolidated the meta issue you've created in Audit Usage collection with high Kibana/ES performance cost for some clusters. Does that sound reasonable?

@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:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:large Large Level of Effort and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort labels Nov 25, 2021
@afharo
Copy link
Member

afharo commented Dec 1, 2021

Should we also tackle #87846? IMHO, it will reduce the number of requests to only 1 every 24h (no matter how many users the cluster has).

@Bamieh
Copy link
Member Author

Bamieh commented Dec 2, 2021

@afharo good one! Added to the list

@afharo
Copy link
Member

afharo commented Jan 4, 2022

Another idea that would improve our visibility of telemetry is #89839. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Telemetry impact:critical This issue should be addressed immediately due to a critical level of impact on the product. loe:large Large Level of Effort Meta Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

4 participants