SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

SigNoz Community

<@U02TULTEF18> it's basically address to reach the endpoint hosting the jvm metrics.

If SigNoz is hosted in the same k8s cluster, then the address should look like DNS resolution of the service hosting metrics

Eg,  `&lt;service-name&gt;.&lt;namespace&gt;.svc.cluster.local:8090`

also the service should expose port `8090` where the prometheus metrics are exposed

Thanks <@U01HWQ1RTC2> but we use two different clusters. one is dedicated to signoz and one for applications.  so i have to point to loadbalancer:8090 of the application cluster?

<@U02TULTEF18> yes, if the loadbalancer is on service level. Might be different for ingress

ok, i'll give it a try and update you thanks

<@U01HWQ1RTC2> Just one more question, but does the same target apply to this conf?

prometheus:
 config:
   scrape_configs:
     - job_name: "otel-collector"
       scrape_interval: 60s
       static_configs:
         - targets: ["otel-collector:8889"]

should i always point to the application cluster?

this is part of SigNoz and should not change

it is supposed to scrape another service in the same cluster where signoz is installed