Hi team , I have installed a Signoz application through Signoz helm in my K8 cluster. Signoz application is up and running fine. I was trying to monitor my spring boot application which is running in same k8 cluster . spring application able to connect with Signoz, I could see my service name in services of Signoz And also I am able to monitor few of the metric https://signoz.io/docs/tutorial/jvm-metrics/#available-metrics-that-you-can-monitor provided in the docs, The Metric related JDBC , HIKARI I not able to monitor and see in dropdown of metrics . as we were jdbc connection and hikari connection in microservice we want those metrics as priority In Microservice level I added few things as per docs I added this dependency in my pom.xml and properties in application.properties <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-actuator</artifactId> </dependency> <dependency> <groupId>io.micrometer</groupId> <artifactId>micrometer-registry-prometheus</artifactId> <scope>runtime</scope> </dependency> management.endpoints.web.exposure.include=prometheus,health,info,metric management.health.probes.enabled=true management.endpoint.health.show-details=always management.endpoint.prometheus.enabled=true please help in getting those mentioned related metrics ( JDBC and HIKARI )

There will be

otel-collector-metrics

pod running in the SigNoz deployment, which scrapes the metrics https://github.com/SigNoz/charts/blob/39bd534401375fc27958ff202e09c2148f6146d2/charts/signoz/values.yaml#L1529. You need to make sure the

scrape_configs

endpoint is set up correctly and reachable from the

otel-collector-metrics

.

Ok , i need to setup by service endpoints in scrape_configs by editing the values.yaml and reinstall signoz helm ?

You can use helm override values.yaml where you make your own changes.

Hi @Srikanth Chekuri i tried to override values.yaml using -->helm -n platform install --repo https://charts.signoz.io signoz/signoz --set otelCollectorMetrics.config.scrape_configs=[job_name: "transformation-ms"] --set otelCollectorMetrics.config.scrape_configs.scrape_interval=60s --set otelCollectorMetrics.config.metrics_path="/transformation-ms/actuator/prometheus" --set otelCollectorMetrics.config.scrape_configs.static_configs=[targets:["transformation-ms.default:3774"]]