This message was deleted.

Slackbot

04/14/2022, 12:44 PM

This message was deleted.

Ankit Nayan

04/14/2022, 1:10 PM

@User it's basically address to reach the endpoint hosting the jvm metrics.

Ankit Nayan

04/14/2022, 1:11 PM

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

Ankit Nayan

04/14/2022, 1:13 PM

Eg,

<service-name>.<namespace>.svc.cluster.local:8090

Ankit Nayan

04/14/2022, 1:14 PM

also the service should expose port

where the prometheus metrics are exposed

edr

04/14/2022, 1:16 PM

Thanks @User 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?

Ankit Nayan

04/14/2022, 1:42 PM

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

edr

04/14/2022, 1:59 PM

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

👍 1

edr

04/14/2022, 2:31 PM

@User 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?

Ankit Nayan

04/14/2022, 2:43 PM

this is part of SigNoz and should not change

Ankit Nayan

04/14/2022, 2:44 PM

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

Open in Slack

Previous Next

SigNoz Community

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