Optionally prefix sample name with database name about influxdb_exporter HOT 4 CLOSED

That sounds more like a label than a part of the metric name to me. Adding a label to everyone using just one database would be annoying though.

from influxdb_exporter.

I'm not sure about this. As far as I can see, in Influx the database is a mandatory top-level grouping. Do we still recommend prefixing metric names by the system that they come from?

@jmcarp in general, I would recommend avoiding this situation by not pushing to the exporter from multiple sources. That also opens up the possibility of conflicting label sets (#23) so I think the ideal deployment is to run the exporter side-by-side with each source process, and deploy them together. Is that a possible solution for your use case?

from influxdb_exporter.

Do we still recommend prefixing metric names by the system that they come from?

From the piece of code, not the particular target. This sounds like a whole-target thing.

from influxdb_exporter.

I'm going to close this because of age. If someone is in this situation, I would recommend to bring the exporter closer to the systems that generate the metrics (run one per source), so that you can distinguish between them in Prometheus' service discovery.

from influxdb_exporter.