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

stack_management collector: review implementation #85811

Closed
afharo opened this issue Dec 14, 2020 · 3 comments · Fixed by #88675
Closed

stack_management collector: review implementation #85811

afharo opened this issue Dec 14, 2020 · 3 comments · Fixed by #88675
Assignees
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 14, 2020

The Usage Collector stack_management was ported from the legacy system and, maybe, we should spend some time reviewing its implementation to provide more valuable data.

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

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

@afharo
Copy link
Member Author

afharo commented Jan 12, 2021

We should add a whitelist of fields to report. That will also help with the finer definition of the schema.

@afharo
Copy link
Member Author

afharo commented Jan 13, 2021

As per late discussions, we're going to attempt to extend the ui_settings API so plugins can specify if a key should not be reported. In those cases, we'll only report a boolean on whether they are set or not.

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

Successfully merging a pull request may close this issue.

3 participants