You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dogstatsd supports two types of tags on metrics: simple and dimensional
tags[^1]. the former is just a key, the latter is a key and a value.
with the assumption that many users of the statsdreceiver are enabling
ingest of dogstatsd metrics, this makes the statsd parser more
optimistic, so it can handle tags w/o a value. this functionality is
gated behind a new `enable_simple_tags` flag.
when this happens, we set an attribute that has a zero value. so far as
i know, this is allowed in the opentelemetry spec. the decision of how
to handle attributes w/ zero values is best left to configuration w/in
the pipeline itself, as different users may have different opinions or
approaches that work best with their systems.
[^1]:
https://www.datadoghq.com/blog/the-power-of-tagged-metrics/#whats-a-metric-tag
**Testing:**
added coverage to unit tests to enable parsing simple tags.
---------
Co-authored-by: Alex Boten <[email protected]>
Copy file name to clipboardExpand all lines: receiver/statsdreceiver/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,8 @@ The Following settings are optional:
33
33
34
34
-`enable_metric_type: true`(default value is false): Enable the statsd receiver to be able to emit the metric type(gauge, counter, timer(in the future), histogram(in the future)) as a label.
35
35
36
+
-`enable_simple_tags: true`(default value is false): Enable parsing tags that do not have a value, e.g. `#mykey` instead of `#mykey:myvalue`. DogStatsD supports such tagging.
37
+
36
38
-`is_monotonic_counter` (default value is false): Set all counter-type metrics the statsd receiver received as monotonic.
37
39
38
40
-`timer_histogram_mapping:`(default value is below): Specify what OTLP type to convert received timing/histogram data to.
0 commit comments