-
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
[Telemetry] Report the Application Usage (time of usage + number of clicks) #57893
Conversation
Pinging @elastic/pulse (Team:Pulse) |
I'm pending some unit tests and I'll release it from the draft status |
b5f03ba
to
4911458
Compare
8f04bb7
to
0eaf763
Compare
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
After speaking with @Bamieh, we agreed it's better to make use of the UI-Metrics reporter. So I'll be migrating some of this logic there and will push an update. |
Closing in favour of #58401 |
Pinging @elastic/kibana-core (Team:Core) |
Summary
Add a plugin that retrieves the time (in minutes) and the number of clicks on each application inside Kibana and report it via telemetry.
It uses its own index to store the grouped events in the form of
{ timestamp, appId, numberOfClicks, minutesOfScreenTime }
. Rolling up the information to saved objects for the entries older than 90 days (because the required reported data has 3 levels of aggregation: 30 days, 90 days and total).The finally reported information to our telemetry service looks like below:
Fixes #52737
Checklist
Delete any items that are not applicable to this PR.
For maintainers