Errors when push standart golang client metrics to influxdb_exporet about influxdb_exporter HOT 4 CLOSED

Just to be clear, you have something that is natively instrumented for Prometheus, but then you are using Telegraf to push them into this exporter? I would rather not support this setup at all tbh, because I don't want to encourage all these additional steps.

Why do you need to do this?

from influxdb_exporter.

In some cases (in example migration period) we need send some data to two destinations: influxdb and prometheus. This need for testing and troubleshooting. Some exporters already have different endpoints for its metrics and scraped from destinations metrics.

from influxdb_exporter.

But even in this transition period, Prometheus can already scrape the targets directly?

from influxdb_exporter.

Not always. In some network isolation topologies exporter is better (and faster) way for testing, rather than federation setup

from influxdb_exporter.