I have had checked already the telegraf prometheus plugin documentation on github, but I am not really able to understand it. Yet I am even not sure, if the plugin interacts with a prometheus exporter/endpoint or a prometheus server instance.
I don’t know any other documentation for the telegraf plugin. So if there is anything else, please share it. I also tried to google some examples, but failed.
Influx2.0 is not really an option for us, since we have now just influx1.7.1 in place and plan to update to the newest version. Maybe 2.0 is something within one or two years, but not now.
We got some short description from the third party software developers, that I have attached. In general I would assume, that it is possible to use this provided information two write a valid telegraf config and then gather all the data, but I failed…
For advanced monitoring purposes, XXX services and clients export their metrics for consumption
by external monitoring systems.
For each service, metrics are available via the built-in HTTP server on the /prometheus page (for
example http: //registry:7871/prometheus). The format is the Prometheus Text format 0.0.4 which
is documented here.
This format can be consumed by Prometheus 1.x and 2.x, but also other monitoring systems are
able to scrape Prometheus targets. XXX Registry services also export a minimal Consul-like
service discovery interface that allows Prometheus to automatically discovery XXX services
11.4.1 Prometheus Configuration Example
An example Prometheus conguration which lists services individually looks like this:
- job_name: "XXX_registry"
Using the service discovery interface, Prometheus discovers clients and services automatically:
- job_name: testing
- server: registry:7871
- source_labels: [job]
- source_labels: [__meta_consul_service]
- source_labels: [__meta_consul_service_address]
Make sure that a server points to an existing registry and the datacenter field is set (to any value).