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

[Telemetry] Kibana config usage schema #97599

Closed
Bamieh opened this issue Apr 20, 2021 · 3 comments
Closed

[Telemetry] Kibana config usage schema #97599

Bamieh opened this issue Apr 20, 2021 · 3 comments
Labels
enhancement New value added to drive a business result Feature:Telemetry impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@Bamieh
Copy link
Member

Bamieh commented Apr 20, 2021

Currently config usage collector schema is excluded from the mapping json files.

This decision was intentional since explicitly typing every config in the collector schema is not practical for devs and adds a lot of maintenance time on the core team.

We'll be experimenting with flattened_type ES type and runtime fields to query this collector. Both are not yet supported by the collection schema types.

If we find flattened_type enough for this use case we would need to support this type in our telemetry tooling. Otherwise if we had to explicitly specify every kibana config in the schema we'd need to improve our telemetry tools to automatically do this for devs. Although flattened_type seems promising enough for this use case.

@Bamieh Bamieh added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc enhancement New value added to drive a business result Team:KibanaTelemetry labels Apr 20, 2021
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-telemetry (Team:KibanaTelemetry)

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Nov 4, 2021
@lukeelmers
Copy link
Member

We will close this for now -- if we get feedback from any teams that are interested in using flattened_type, we can re-open or create a new issue. But at the moment, we are not aware of anyone that needs this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Telemetry impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

3 participants