Skip to content

[inputs.statsd] Splitting ':', unable to parse metric: _sc|jmxfetch-config.can_connect|0 #17480

@dacosnguyen

Description

@dacosnguyen

Relevant telegraf.conf

[[inputs.statsd]]
datadog_distributions = true
datadog_extensions = true
delete_counters = true
delete_gauges = true
delete_sets = true
delete_timings = true
max_ttl = "30s"
number_workers_threads = 50
percentiles = []
sanitize_name_method = "upstream"
service_address = "[REDACTED]"

Logs from Telegraf

telegraf[REDACTED]: [REDACTED] E! [inputs.statsd] Splitting ':', unable to parse metric: _sc|jmxfetchconfig.can_connect|0
telegraf[REDACTED]: [REDACTED] E! [inputs.statsd] Splitting ':', unable to parse metric: _sc|jmxfetch-config.can_connect|0

System info

Telegraf 1.28.5, Linux [REDACTED] 6.12.23 #1-NixOS SMP PREEMPT_DYNAMIC [REDACTED] x86_64 GNU/Linux

Expected behavior

I expect the datadog service check metric will be parsed without a problem while having the config datadog_extensions = true.

Actual behavior

telegraf[REDACTED]: [REDACTED] E! [inputs.statsd] Splitting ':', unable to parse metric: _sc|jmxfetchconfig.can_connect|0
telegraf[REDACTED]: [REDACTED] E! [inputs.statsd] Splitting ':', unable to parse metric: _sc|jmxfetch-config.can_connect|0

Additional info

It’s also weird that there’s jmxfetch-config and then jmxfetchconfig (without hyphen) , but the latter one may be some our internal thing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugunexpected problem or unintended behavior

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions