Describe the enhancement:
As part of the efforts for decoupling Monitoring & Telemetry in Kibana (elastic/kibana#83626), we are stopping the collection of usage data (elastic/kibana#83521), meaning we'll only collect metric-related stats from 7.11 and future versions.
This can be achieved by always sending exclude_usage=true when requesting the API /api/stats?extended=true&legacy=true&exclude_usage=true (line where we control it).
Describe a specific use case for the enhancement or feature:
Currently, the stats dataset in the Metricbeat-Kibana module collects the extended usage details every 24h so the Monitoring plugin store it in the .monitoring-kibana-* indices. These usage details are not actually used by the Monitoring plugin itself to anything other than reporting telemetry.
With the rise of the local telemetry, monitoring-sourced telemetry doesn't need to report this data anymore, so we can disable the collection in the 2 sources of information for the Monitoring plugin:
Describe the enhancement:
As part of the efforts for decoupling Monitoring & Telemetry in Kibana (elastic/kibana#83626), we are stopping the collection of usage data (elastic/kibana#83521), meaning we'll only collect metric-related stats from 7.11 and future versions.
This can be achieved by always sending
exclude_usage=truewhen requesting the API/api/stats?extended=true&legacy=true&exclude_usage=true(line where we control it).Describe a specific use case for the enhancement or feature:
Currently, the
statsdataset in the Metricbeat-Kibana module collects the extended usage details every 24h so the Monitoring plugin store it in the.monitoring-kibana-*indices. These usage details are not actually used by the Monitoring plugin itself to anything other than reporting telemetry.With the rise of the
localtelemetry,monitoring-sourced telemetry doesn't need to report this data anymore, so we can disable the collection in the 2 sources of information for the Monitoring plugin: