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

splunkmetric serializer doesn't properly support bool values #5006

Closed
ronnocol opened this issue Nov 19, 2018 · 0 comments · Fixed by #5008
Closed

splunkmetric serializer doesn't properly support bool values #5006

ronnocol opened this issue Nov 19, 2018 · 0 comments · Fixed by #5008
Labels
bug unexpected problem or unintended behavior
Milestone

Comments

@ronnocol
Copy link
Contributor

Relevant telegraf.conf:

[[outputs.file]]
files = ["stdout"]
data_format = "splunkmetric"
[[inputs.docker]]

System info:

Telegraf unknown (git: master f175848)
Linux or OSX
Splunk 7.1+ (with metrics support)

Steps to reproduce:

  1. Run telegraf with an input that produces a bool (e.g. inputs.docker)
  2. Watch Splunk be sad with a non-numeric metric value

Expected behavior:

The metric is either converted into a valid value (1 for true, 0 for false) or dropped like string values are.

Actual behavior:

Serializer tries to send the metric to Splunk causing an ingest error.

Additional info:

Reported to me on the Splunk Slack channels by guilhem.marchand

ronnocol added a commit to ronnocol/telegraf that referenced this issue Nov 19, 2018
Strings are still dropped, bools are set to 1 for true and 0 for false
Solves: influxdata#5006
@danielnelson danielnelson added this to the 1.10.0 milestone Nov 19, 2018
@danielnelson danielnelson added the bug unexpected problem or unintended behavior label Nov 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants