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

telegraf fails to handle negative inputs since 1.2.0 #2324

Closed
faheus opened this issue Jan 26, 2017 · 1 comment · Fixed by #2347
Closed

telegraf fails to handle negative inputs since 1.2.0 #2324

faheus opened this issue Jan 26, 2017 · 1 comment · Fixed by #2347
Assignees
Labels
bug unexpected problem or unintended behavior
Milestone

Comments

@faheus
Copy link

faheus commented Jan 26, 2017

Bug report

Since the update to Version 1.2.0, the mqtt_consumer plugin fails to fetch negative numbers

Relevant telegraf.conf:

[[inputs.mqtt_consumer]]
servers = ["localhost:1883"]
qos = 0

   topics = [
     "lab/sensor/#",
     "office/sensor/#"
   ]

     persistent_session = true

     client_id = "telegraf"
    username = "telegraf"
    password = ""
   data_format = "value"
   data_type = "float"

System info:

Telegrav v1.2.0, Debian Jessie.

Steps to reproduce:

  1. configure output.file to output in /tmp/metrics.out
  2. tail -f on that file
  3. Publish a negative Value in an MQTT Topic -> No output in this file
  4. Publish a positive Value in an MQTT Topic -> gets shown: mqtt_consumer,topic=office/sensor/esp_0f4b61/temperature,host=host value=21.8125 1485459636345140907

Expected behavior:

As in a previous Version, it should deliver also the Negative Values.

Additional info:

The configfile didn't change in the Update.

@faheus faheus changed the title mqtt_consumer fails to handle negative inputs sind 1.2.0 mqtt_consumer fails to handle negative inputs since 1.2.0 Jan 26, 2017
@sparrc sparrc added the bug unexpected problem or unintended behavior label Jan 27, 2017
@sparrc sparrc added this to the 1.2.1 milestone Jan 27, 2017
sparrc added a commit that referenced this issue Feb 1, 2017
@sparrc sparrc changed the title mqtt_consumer fails to handle negative inputs since 1.2.0 telegraf fails to handle negative inputs since 1.2.0 Feb 1, 2017
@sparrc
Copy link
Contributor

sparrc commented Feb 1, 2017

can confirm that this is affecting all plugins using the influx parser, will have a fix and a 1.2.1 release available soon

sparrc added a commit that referenced this issue Feb 1, 2017
sparrc added a commit that referenced this issue Feb 1, 2017
maxunt pushed a commit that referenced this issue Jun 26, 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.

3 participants