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

[Usage Collection] Collect Feature Usage #86875

Open
afharo opened this issue Dec 23, 2020 · 5 comments
Open

[Usage Collection] Collect Feature Usage #86875

afharo opened this issue Dec 23, 2020 · 5 comments
Labels
Feature:Telemetry Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@afharo
Copy link
Member

afharo commented Dec 23, 2020

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.

@afharo afharo added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:Telemetry labels Dec 23, 2020
@elasticmachine
Copy link
Contributor

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

@pgayvallet
Copy link
Contributor

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

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.

@afharo
Copy link
Member Author

afharo commented Jan 7, 2021

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 :)

@afharo
Copy link
Member Author

afharo commented Mar 24, 2021

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 :)

@Bamieh
Copy link
Member

Bamieh commented Mar 30, 2021

Adding . to follow up once the server counters feature is merged :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Telemetry 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