-
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
Not Writing SNMP Data to Influx #4326
Comments
same problem with centos 7.5, telegraf-1.7.0-1, influxdb-1.5.2-1 |
Same problem with raspbian stretch. Upgraded to telegraf 1.7 and now not all of my network stats are making their way into influx influxdb 1.5.2 [Update: it looks like its getting written but the tagging has changed so I can no longer filter by ifName in grafana] |
@Audiobuzz Can you run |
I'm seeing the same issue. network_interface is fine, but network_interface_x doesn't get there. Telegraf 1.7:
Telegraf 1.6.1:
|
@mpetersen42 So when running Telegraf 1.7, |
@danielnelson Technically you'd need a WHERE clause with a switchname collected by 1.7.0 and a time range after the 1.7.0 upgrade to get no results, but yes. network_interface_stats was fine as well. |
@mpetersen42 Could you test with 1.6.4? This version introduced the change between your two output samples. (ifName is only added as a tag) |
1.6.4 is NOT working.
|
Here's my SNMP config (in /etc/telegraf/telegraf.d/):
|
Interesting, could you check 1.6.3 too then? |
@danielnelson 1.6.3 seems to work.
|
So it was broken in 1.6.4, but whats odd is that both of these metrics are valid. Perhaps the data is still being added but the query you are using is now broken. For instance, if you were doing this before:
I believe you will now need to do this because ifName is only a tag:
|
I guess it is something with the query. I've always had ifName setup as a tag (see config above) so I don't know exactly what is going on or why the query results are different. With a fresh install of Telegaf 1.7.1 and InfluxDB 1.5.4 this gets results:
And this gets the same results:
But on the existing install with Telegraf 1.7.1 and InfluxDB 1.5.4 this is empty:
While this gets expected results:
|
I believe this was accidentally caused by #4203, in which we fixed a bug that was causing snmp fields marked with The requirement to add
So in my case I would need to wait up to 168h and then any queries for this time and newer should work as before. There isn't really a smooth way to transition from the prior situation without rewriting your historical data, even if we add a config switch it won't be possible to gradually migrate away. I believe it may be best to modify your queries to use However, I know this will be an issue for some to update all queries. I wonder if we should add an option that would cause queries to continue to add tags and both tags and fields? |
In some examples, it would be nice to have tags also entered as values. In Grafana Dashboards, singlestat plugin cannot display tag values, only the field values. With dynamic dashboards (with variables), I was trying to show my tag value somewhere in the dashboard. Should this fix be optionnal? (with a parameter like is_tag_and_value = true)? |
@Touchedegris I don't think we will add an option for this, and instead rely on the query workaround. I think you should be able to duplicate your tag to a field though using a combination of the |
Relevant telegraf.conf:
telegraf.conf Changes:
Example SNMP Conf:
System info:
CentOS 6.9 64-Bit
Telegraf v1.7.0 (git: release-1.7 f4d22dd)
InfluxDB v1.5.2 (git: 1.5 02d7d4f043b34ecb4e9b2dbec298c6f9450c2a32)
Steps to reproduce:
Start Influx (with a default config) and Telegraf with SNMP configs in the telegraf.d folder.
Expected behavior:
SNMP data is stored in Influxdb like normal, so Grafana can extract and display it.
Actual behavior:
Influx will get the POST data for SNMP, acknowledge it with an HTTP response code 204, but not write it to disk, which results in Grafana not being able to show networking graphs, however my DNS and HTTP monitors work just fine.
Additional info:
My telegraf and influxdb are for the most part stock installs, with the only change to recently being a reboot of the server, and I'm puzzled on where to go on troubleshooting since strace on Influx forks off into oblivillian so I can't see where the problem is coming from.
CentOS 6
Grafana, Influx, and Telegraf were installed from their respective YUM repositories.
P.S. --debug and --test do not show any errors whatsoever.
The text was updated successfully, but these errors were encountered: