Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Statsd input plugin crashing #6075

Closed
diraol opened this issue Jul 5, 2019 · 0 comments · Fixed by #6088
Closed

Statsd input plugin crashing #6075

diraol opened this issue Jul 5, 2019 · 0 comments · Fixed by #6088
Labels
area/statsd bug unexpected problem or unintended behavior
Milestone

Comments

@diraol
Copy link

diraol commented Jul 5, 2019

Relevant telegraf.conf:

[[inputs.statsd]]
  protocol = "udp"
  service_address = ":8123"
  delete_gauges = true
  delete_counters = true
  delete_sets = true
  delete_timings = true
  percentiles = [90, 95, 99]
  metric_separator = "."
  datadog_extensions = true
  allowed_pending_messages = 10000
  percentile_limit = 1000

System info:

Telegraf: 1.11.1 (docker version)
OS: Ubuntu 14.04
Datadog agent version: 1:5.32.4-1

Steps to reproduce:

  1. Run telegraf with statsd plugin enabled (and parsing datadog_extensions).
  2. Configure a datadog agent to send metrics to telegraf/statsd.
  3. Send invalid metrics to datadog agent (from telegraf/statsd perspective).

Metric example:

measure.outgoing_requests.response.size:-1.000000|h

Expected behavior:

telegraf/statsd should log this message (preferably as a warning message, but it can be as error message) and keep going.

Actual behavior:

telegraf/statsd just blows up.

Additional info:

Error Logs:

image

@danielnelson danielnelson added this to the 1.11.2 milestone Jul 5, 2019
@danielnelson danielnelson added area/statsd bug unexpected problem or unintended behavior labels Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/statsd bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants