Getting prometheus Job_Name as metric dimension in OpenTelemetry Collector #8221
debashish-github
started this conversation in
General
Replies: 1 comment
-
Any updates on this ? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
We have a microservices based architecture for our application and each application has its prometheus scrape end point . We use open telemetry collector to convert the prometheus metric to opentelemetry format and send it to the consuming telemetry system.
Our configuration for open telemetry collector is attached .
Now since we are running a single deployment of our openTelemetry collector we need to differentiate the metrics between the different microservices app . As visible in the config each of the app has its own scrape enpoint and a job name.
We want to associate the job_name to the metric that is emitted. Prometheus has inbuild metric dimension called job_name.
Does opentelemetry provide a way to add this job_name to each metric so that the metrics from different microservices app can be differenciated ?
Thanks
config.txt
Beta Was this translation helpful? Give feedback.
All reactions