[Telemetry] Kibana config usage schema #97599
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
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.The text was updated successfully, but these errors were encountered: