You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I setup database routing. Every service (MySQL, RabbitMQ and Jenkins) should use it's own database in InfluxDB. The used config is attached.
This works good so far.
If I restart the influxdb service the routing is broken for 3 to 4 data points (Interval is 10s).
This means that every collected data point is written to every configured database.
I got 3 to 4 MySQL, RabbitMQ and Jenkins data points in my MySQL database.
I got 3 to 4 MySQL, RabbitMQ and Jenkins data points in my RabbitMQ database.
I got 3 to 4 MySQL, RabbitMQ and Jenkins data points in my Jenkins database.
This is not a very critical error but it's causing confusion.
Also I am not sure if this is a problem with Telegraf, because InfluxDB is also involved.
I could not find any logs related to this. There are lines like read: connection reset by peer. But that's what I'm expecting.
This will actually be more efficient even when the bug is fixed because only the metrics that match tagpass are added to the output's metric buffer. With the original configuration all metrics are added to every output's metric buffer and then written to the database depending on the influxdb_database tag.
I setup database routing. Every service (MySQL, RabbitMQ and Jenkins) should use it's own database in InfluxDB. The used config is attached.
This works good so far.
If I restart the influxdb service the routing is broken for 3 to 4 data points (Interval is 10s).
This means that every collected data point is written to every configured database.
This is not a very critical error but it's causing confusion.
Also I am not sure if this is a problem with Telegraf, because InfluxDB is also involved.
I could not find any logs related to this. There are lines like
read: connection reset by peer
. But that's what I'm expecting.Relevant telegraf.conf:
System info:
1.12.0
as Docker ContainerSteps to reproduce:
Expected behavior:
Every database should contain its own measurements.
Actual behavior:
A small amount of values get the wrong database.
The text was updated successfully, but these errors were encountered: