-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
input hddtemp: Strange data? Why not just use value? #1904
Milestone
Comments
cc @mendelgusmao |
3 tasks
Sorry for not noticing this before. It was my first PR. hddtemp's plugin implementation was based off of sensors plugin. I agree with the changes proposed by @jonaz and am willing to accept a PR at MendelGusmao/go-hddtemp. |
jonaz
added a commit
to jonaz/telegraf
that referenced
this issue
Dec 13, 2016
Added unit tests for the changes Fixes influxdata#1904
sparrc
pushed a commit
that referenced
this issue
Dec 13, 2016
Added unit tests for the changes Fixes #1904
njwhite
pushed a commit
to njwhite/telegraf
that referenced
this issue
Jan 31, 2017
…data#1905) Added unit tests for the changes Fixes influxdata#1904
maxunt
pushed a commit
that referenced
this issue
Jun 26, 2018
Added unit tests for the changes Fixes #1904
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Relevant telegraf.conf:
System info:
Telegraf - version 1.0.1
ubuntu 14.04
Steps to reproduce:
Expected behavior:
The temperature should be in the value field and not a new field for each disk?
Actual behavior:
The text was updated successfully, but these errors were encountered: