Ragulraj
04/13/2023, 4:01 AMSrikanth Chekuri
04/13/2023, 6:20 AMjdbc-datasource.enabled=trueThis is not related to the metric.
jdbc-datasource
which creates spans whenever the java.sql.DataSource#getConnection
method is called. https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/b594b7f6f9936758294f11d172b41408a00cb7f0/docs/supported-libraries.md#d[…]s
Where is the source of metrics data? like micrometer or OTEL native or something else?db_client_connections_usage
with state either idle
/`used` and there are several other which can be found here https://github.com/open-telemetry/opentelemetry-specification/blob/25f513dbea2810b[…]/specification/metrics/semantic_conventions/database-metrics.mdRagulraj
04/13/2023, 7:15 AM#!/bin/bash
java -Dlog-path=/logs -Dspring.config.location=file:/properties/fincluez-l2t-ms.yml,file:/properties/fincluez-t-ms-loan.yml -Dlogging.config=file:/properties/logback-spring-loan.xml -javaagent:/opentelemetry/opentelemetry-javaagent.jar -Dotel.metrics.exporter=none -Dotel.exporter.otlp.endpoint=http://${signoz_ip} -Dotel.instrumentation.jdbc-datasource.enabled=true -Dotel.resource.attributes="service.name=fincluez-l2t-loans" -jar loans-l2t-22.2.0-0.1.war
i gave those while running service , do i need to change Dotel.instrumentation.jdbc-datasource.enabled=true to Dotel.instrumentation.db.client.connections.usage=idle like this ?Srikanth Chekuri
04/13/2023, 7:18 AMdo i need to change Dotel.instrumentation.jdbc-datasource.enabled=true to Dotel.instrumentation.db.client.connections.usage=idle like this ?The
db_client_connections_usage
is a metric name, not a configuration option.
Remove this if you want metrics. If this is from our docs/blogs we will get it updated.Copy codeDotel.metrics.exporter=none
Ragulraj
04/13/2023, 9:49 AMSrikanth Chekuri
04/13/2023, 10:01 AMRagulraj
04/13/2023, 11:33 AMSrikanth Chekuri
04/13/2023, 11:35 AMRagulraj
04/13/2023, 11:37 AMSrikanth Chekuri
04/13/2023, 11:39 AMRagulraj
04/13/2023, 11:41 AMSrikanth Chekuri
04/13/2023, 1:06 PMfailed to scrape prometheus endpointYou need to fix this. Make sure the endpoint you are configuring is correct and reachable by collector.
Ragulraj
04/14/2023, 7:24 AMSrikanth Chekuri
04/14/2023, 7:43 AMRagulraj
04/14/2023, 9:34 AMSrikanth Chekuri
04/14/2023, 11:53 AM10.53.34.50
and port 8090
you can verify if it emits metrics by curling with curl <http://10.52.34.50:8090/actuator/prometheus>
. And since there is already metric_path: "/actuator/prometheus"
covered in config, in the target you just need to provide host:port
where port is 8090
and host
is the host address where application service is running.Ragulraj
04/17/2023, 10:04 AMSrikanth Chekuri
04/17/2023, 11:17 AMeventhough it is showing failing to scrape , i am able to get other metrics except jdbc and hikariThe jdbc and hikari metrics are coming from the micrometer and need to be scraped. The rest of the metrics could be coming from OTLP.
can u give me hint , that were i need to check failed to scrapeThis is mostly like a network issue. Please make sure the host and port are correct and are reachable to the SigNoz collector.
Ragulraj
04/18/2023, 10:11 AM<dependency>
<groupId>io.opentelemetry</groupId>
<artifactId>opentelemetry-api</artifactId>
</dependency>
<dependency>
<groupId>io.opentelemetry</groupId>
<artifactId>opentelemetry-api-metrics</artifactId>
<version>1.9.1-alpha</version>
</dependency>
Srikanth Chekuri
04/18/2023, 12:25 PMmetrics_path
in the configuration then should be /alpha-transformation-ms/actuator/prometheus
Ragulraj
04/18/2023, 12:36 PMSrikanth Chekuri
04/18/2023, 12:51 PMcurl -X GET 10.53.34.50:3774/alpha-transformation-ms/actuator/prometheus
from the collector host, does it resolve and return any data? Did you have the micrometer setupRagulraj
04/19/2023, 3:43 AM