Closed
Description
Component(s)
receiver/statsd
Describe the issue you're reporting
When using recent versions of the DogStatsD client (e.g. Java client) I noticed that metrics sent by the client weren't captured by the statsd
receiver. The cause of this issue boils down to the statsd
receiver rejecting metrics that contain unrecognized parts, and DogStatsD emits metrics with extra fields that are currently unsupported by the receiver.
In particular, there are 2 new fields that are currently unsupported by the receiver:
Example of a metric that the statsd
receiver drops due to the unrecognized parts:
workflow_execution.failure:1|c|#workflow.version:2,workflow.name:Telemetry 2|c:abc123"