-
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
Telegraf 0.2.2 panic #389
Comments
@rvrignaud What plugins and outputs are you using? Only the prometheus plugin & influxdb output? Are the values actually NaN? How do they appear in influxdb? |
I have only influxdb output (I use influxdb 0.9.4.1) and only prometheus plugin (an array with 13 urls). |
@rvrignaud I'm just trying to understand what the NaN metrics actually look like when they reach InfluxDB. When using Telegraf 0.1.9, could you make a query on a NaN metric and show me how it looks in the DB? Something simple like |
Others queries are working fine |
@rvrignaud I see, it looks like InfluxDB 0.9.5 has begun explicitly banning NaN values, because it has never actually supported them anyways. I think the fix is going to be for Telegraf to just drop the NaNs before trying to even create points out of them. It looks like the panic is coming from the influxdb client so that should probably be fixed as well in the influxdb repo. |
@rvrignaud 0.2.3 is now available and this is fixed |
Hello,
I'm using telegraf to scrape prometheus' kubernetes endpoints.
I tried to upgrade my telegraf from 0.1.9 to 0.2.2.
It panicked after complaining a lot about NaN. Please find the logs below.
I'm happy to provide more informations and help in debugging if needed.
I did a rollback to 0.1.9: no complain about NaN and no panic.
The text was updated successfully, but these errors were encountered: