-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Simplify visualization telemetry #56986
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
@flash1293 At the time this was implemented, the usage collector was being called from a user's browser if needed, and the goal of the usage collectors was to be as fast as possible- this is why the actual aggregation was done separately, and then the results were saved. Has something about this changed so that the usage collector can do more work? This might be a question for members of @elastic/pulse |
If the task takes too long then caching it every 24 hours makes sense. If it does not take too long then it is OK to fetch usage on the spot. The telemetry is sent at least once every 24 hours and when users click on the example flyout. If lens is only doing ES queries i believe there would be no need to cache the requests. |
@lukeelmers For telemetry of "Visualize visualizations" it looks like it would make sense to move the telemetry into the |
Agreed, this was a bit of an ambiguous item anyway when we started migration, but as it tracks usage for all of visualizations, the cc @ppisljar in case he feels otherwise |
Currently the telemetry for OSS visualizations is using the task manager to run an aggregation job daily collecting telemetry data. As the telemetry service itself makes sure to only run once a day it's not necessary to use the task manager directly anymore - instead, the whole task collecting the data can run directly in the usage collector.
Without task manager the
oss_telemetry
does not depend on task manager anymore, it can get moved into thevisualizations
plugin as a service.The text was updated successfully, but these errors were encountered: