Investigate DogStatsD internal telemetry config: `telemetry.dogstatsd.*` and `telemetry.dogstatsd_origin`.

[jszwedko]

Problem

The core agent exposes four config keys for fine-tuning DogStatsD internal telemetry:

• telemetry.dogstatsd.aggregator_channel_latency_buckets — histogram buckets for DSD-to-aggregator channel lag
• telemetry.dogstatsd.listeners_channel_latency_buckets — histogram buckets for listener packet-channel latency
• telemetry.dogstatsd.listeners_latency_buckets — histogram buckets for listener processing latency
• telemetry.dogstatsd_origin — enables per-UDS-origin breakdown of dogstatsd.processed counters

The first three tune Prometheus histogram bucket boundaries for Go-channel-based latency metrics. ADP uses a Tokio async topology with no equivalent channel stage.

telemetry.dogstatsd_origin is a real feature gap: it adds per-origin labels to processed-metric counters, which is relevant for debugging origin detection in production.

What needs to happen

For telemetry.dogstatsd_origin: determine whether ADP's OpenMetrics endpoint already exposes per-origin counters, and if not, whether it should.

For the histogram bucket keys: determine whether ADP has equivalent latency histograms that expose configurable buckets, or whether these are not applicable to ADP's architecture.