Telegraf writes to two InfluxDB databases same data

I have the following config in my telegraf for InfluxDB:

[[outputs.influxdb]]
urls = [“http://127.0.0.1:8086”]
database = “servers”

Yet it’s writing to servers and telegraf databases. How do I make it just write to the servers database?

Please provide the full telegraf log with debug.

Most likely you have a second influxdb v2 stanza somewhere or a second agent running somewhere that is writting there as well :wink:

No this is not the case. I have the following configured:

[[outputs.influxdb]]
urls = [“http://10.20.108.19:8086”]
database = “snmp_metrics”
retention_policy = “”
write_consistency = “any”
timeout = “5s”
namepass = [“snmp”]

I dropped the snmp measurement in the telegraf database. When I drop the snmp measurement from the telegraf database it recreates the measurement and still enters the same data in the snmp measurement in the telegraf database as the snmp_metrics database. This is the only place snmp is configured for Telegraf to poll from

Please provide the logs with debug enabled

I did but nothing but the MIBs are showing

What should I be looking for in the logs?

There’s nothing in the logs about what database it uses

If you want help you need to provide information. I have asked for logs twice, you did not provide them. You also did not provide your full config, so I have no idea what actually have configured for your scenario.

As I mentioned above this is commonly due to someone having a second v2 stanza in their config they didn’t realize was there. Telegraf is not going to suddenly start writing to a second database you haven’t configured.

Additional scenarios include:

  • Accidently running telegraf manually with a different config and not realizing it
  • Running telegraf manually or via a cron, but also running it as a service, or vis-versa
  • Old versions of telegraf had a default influxdb stanza enabled

I would provide the logs you asked for if it was producing logs that are useful. The only thing is displaying are MIB objects. These cannot be passed due to security concerns