I am using StatsD to send metrics to a receiver, but I am encountering an issue where timing metrics (|ms) are not being captured, even though counter metrics (|c) work fine on Splunk Observability...
See more...
I am using StatsD to send metrics to a receiver, but I am encountering an issue where timing metrics (|ms) are not being captured, even though counter metrics (|c) work fine on Splunk Observability Cloud. Example of Working Metric: The following command works and is processed correctly by the StatsD receiver: echo "test_Latency:42|c|#key:val" | nc -u -w1 localhost 8127 Example of Non-Working Metric: However, this command does not result in any output or processing: echo "test_Latency:0.082231|ms" | nc -u -w1 localhost 8127 Current StatsD Configuration: Here is the configuration I am using for the receiver by following the doc: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/statsdreceiver receivers:
statsd:
endpoint: "localhost:8127"
aggregation_interval: 30s
enable_metric_type: true
is_monotonic_counter: false
timer_histogram_mapping:
- statsd_type: "histogram"
observer_type: "gauge"
- statsd_type: "timing"
observer_type: "histogram"
histogram:
max_size: 100
- statsd_type: "distribution"
observer_type: "summary"
summary:
percentiles: [0, 10, 50, 90, 95, 100] Why are timing metrics (|ms) not being captured while counters (|c) are working, can you please help to check on it as the statsdreceiver github document says it supports "timer" related metrics https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/statsdreceiver/README.md#timer Any help or suggestions would be greatly appreciated. Thank You.