-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Usage Collection] Collect Feature Usage #86875
Comments
Pinging @elastic/kibana-core (Team:Core) |
Yea, for the initial version of the feature, using only memory storage was considered acceptable due to the fact that only the time of the last usage of the licensed features is used. If we need to aggregate stats around that, using a more persistent storage will probably be necessary. |
I recall @kobelb had some thoughts around that. I think he suggested to persist it only for telemetry purposes, leaving the current behaviour for external users unchanged. But I may have misunderstood :) |
I think that we may be able to implement this in a fairly easy way once we've got the Server Counters @Bamieh is working on :) |
Adding |
In #60984 we added an API to keep track of the usage of features. We should create a usage collector to report that info in the telemetry payloads.
N.B.: The data returned by the existing APIs is kept in-memory. Server restarts might affect the results. We might want to consider persisting the telemetry-to-be data in a saved object if necessary.
The text was updated successfully, but these errors were encountered: