-
|
Hi, I'm trying to deploy multiple Jaeger instances (one per namespace) in the same K8s cluster for a multi-tenant application. Current Behavior: However, the Monitor (APM) tab aggregates metrics from all Jaeger instances. Root Cause: Attempted Fix: But this only changes the service name for Jaeger's own metrics (port 8888), not the application metrics(port 8889). Changing the deployment name on each NS work, however I want to have the same name for each deployment. Question: Any help would be greatly appreciated! Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hi @wansors! I'm Dosu and I’m helping the jaeger team. Based on the available documentation and configuration files, there is currently no documented way to configure the Prometheus exporter (port 8889) in Jaeger to use a unique There are also no relevant discussions or issues in the Jaeger repository addressing this specific need. At this time, changing the deployment name per namespace remains the only effective workaround to differentiate metrics in Prometheus, even though you prefer to keep the deployment names the same. If you require strict separation of metrics by tenant, you may need to rely on Kubernetes labels, Prometheus relabeling, or other Prometheus-side mechanisms to distinguish between instances. If you have further constraints or requirements, please share them, and I can help look for alternative approaches. To reply, just mention my name @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for your response. After reviewing the code for the different options available, I found that I can use namespaces with both the Prometheus exporter and metric_backend. I successfully implemented namespace separation for a single Prometheus instance, though it required a small adjustment since Jaeger uses a default namespace called "traces_span_metrics" for exported metrics. Here's the working configuration: |
Beta Was this translation helpful? Give feedback.
Hi, thanks for your response.
After reviewing the code for the different options available, I found that I can use namespaces with both the Prometheus exporter and metric_backend. I successfully implemented namespace separation for a single Prometheus instance, though it required a small adjustment since Jaeger uses a default namespace called "traces_span_metrics" for exported metrics.
Here's the working configuration: