error occur when configured as heapster --sink about influxdb_exporter HOT 4 CLOSED

There's no need to use influxdb or heapster in this case. All the relevant parts of Kubernetes can be scraped by Prometheus directly.

from influxdb_exporter.

I just want to compare al the possibility of monitoring.

and then what is the use case for this application ?

from influxdb_exporter.

It's meant for individual applications more than an entire other monitoring system.

from influxdb_exporter.

The fundamental problem is that Kubernetes allows varying label sets while Prometheus (at least the Go client library) doesn't. This is another instance of #23.

The use case for the influxdb exporter is for when you have something that is instrumented for InfluxDB and you have no way of instrumenting it for Prometheus directly. Since all Kubernetes components are instrumented for Prometheus already, you really don't need it, and I'd rather not re-solve the label set issue here.

from influxdb_exporter.