Today telemetry is collected from a variety of endpoints:

• cluster stats /_cluster/stats
• cluster info /
• X-Pack usage /_xpack/usage
• license info /_license

There are two problems with this approach:

• first, it's unclear to our users what information is used for telemetry
• secondly, it's unclear internally that these endpoints are for telemetry, which means from time to time we consider making changes to these endpoints that would either remove information that is useful from a telemetry perspective, or would add information that would not be useful from a telemetry perspective

If we had a single dedicated endpoint that exposed telemetry information, it would clear up some of the confusion around this, and simplify the implementation within Kibana.

There are open questions around how we expose telemetry from X-Pack in a single endpoint that would be defined in core, but @rjernst has some ideas around this that sound promising here.

Relates #52975