Global labels about client_java HOT 5 CLOSED

That's an anti-pattern, target labels should be provided at the Prometheus level via relabelling rather than from clients or exporters.

from client_java.

Thanks! This might solve half my use case. Can you point me to some examples of relabelling_config?

But take the case of env=beta/qa/prod, in a dynamic environment such as AWS, its impossible to have static relabelling config. How do you propose I fix this?

from client_java.

You can use EC2 tags for example to determine you labels. See http://www.robustperception.io/automatically-monitoring-ec2-instances/

from client_java.

Well, that is out of the window! We are using tags for everything and as a result the tags API is throttled when we are spinning up machines rapidly. We are currently implementing the SD as a hack for now and will move to consul soon.

Hmm, I think I will make a wrapper over the Prometheus collectors that would automatically insert such info. Hope moving to consul will fix most of the issues of the peculiar use-case we have.

Thanks!

from client_java.

Consul tags are a list rather than key/value so while you can use them with relabelling it's a bit more difficult.

from client_java.