SigNoz Community

SigNoz Community

Command MenuMenu

K

#support

Monitoring JVM Metrics with Signoz in Kubernetes Cluster

TLDR Ragul had trouble monitoring JVM metrics in their Kubernetes cluster with Signoz using Helm. Srikanth advised modifying the scrape config in values.yaml and checking the host:port/path.

Powered by Struct AI

12

3mo

Jun 05, 2023 (3 months ago)

Photo of md5-001a6b8b05601dc8ac56c5f364768cc1

Ragul

05:31 PM

Hi team , I've just installed signoz in k8s cluster using helm. i need to monitor metrics for my spring boot microservice ,and I can see my microservice name in services section for that i was trying to monitor metrics listed in link https://signoz.io/docs/tutorial/jvm-metrics/#available-metrics-that-you-can-monitor . in this i am getting values for only few metrics for other i am not getting data i have added screenshot of metric which i am not getting data , should i add additional config for this metrics . please suggest some solution for getting this metrics value

Image 1 for Hi team , I've just installed signoz in k8s cluster using helm. i need to monitor metrics for my spring boot microservice ,and I can see my microservice name in services section for that i was trying to monitor metrics listed in link <a href="https://signoz.io/docs/tutorial/jvm-metrics/#available-metrics-that-you-can-monitor" target="_blank">https://signoz.io/docs/tutorial/jvm-metrics/#available-metrics-that-you-can-monitor</a> . in this i am getting values for only few metrics for other i am not getting data i have added screenshot of metric which i am not getting data , should i add additional config for this metrics . please suggest some solution for getting this metrics value

Jun 06, 2023 (3 months ago)

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

12:47 AM

What does your scrape config look like? There is probably some n/w issue while scraping.

Photo of md5-001a6b8b05601dc8ac56c5f364768cc1

Ragul

04:14 AM

scrape config is default one from helm values.yaml . i have not did any changes

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

07:47 AM

The default one from values.yaml doesn’t scrape the metrics exposed by general applications. You need to configure it with the endpoints where you applications emit metrics.

Photo of md5-001a6b8b05601dc8ac56c5f364768cc1

Ragul

10:32 AM

OK

10:32

Ragul

10:32 AM

https://signoz.io/docs/tutorial/jvm-metrics/#configure-signoz-otel-collector-to-scrape-prometheus-metrics i should add promethus config in values.yaml ?

10:34

Ragul

10:34 AM

if yes , please help me in overiding the values.yaml

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

11:24 AM

Yes, you need to add an additional scrape config in values.yaml. It would look like following.

otelCollectorMetrics:
  config:
    receivers:
      # prometheus scrape config
      prometheus:
        config:
          scrape_configs:
            ... <existing_configs_here>
            - job_name: 'applications-metrics'
              scrape_interval: 10s
              metrics_path: <your probe endpoint>
              static_configs:
              - targets:

Photo of md5-001a6b8b05601dc8ac56c5f364768cc1

Ragul

04:59 PM

I added this above config in values.yaml , and upgraded helm using the command -> helm -n platform upgrade my-release signoz/signoz -f values.yaml . but still i am not getting those above mentioned metrics

Image 1 for I added this above config in values.yaml , and upgraded helm using the command -> helm -n platform upgrade my-release signoz/signoz -f values.yaml . but still i am not getting those above mentioned metrics

05:01

Ragul

05:01 PM

for cross check in signoz clickhouse i tried with -> SELECT name
FROM
(
SELECT DISTINCT JSONExtractString(labels, 'name') AS name
FROM signoz_metrics.time_series_v2
) AS tmp1
WHERE name ILIKE '%jdbc%' with this query

05:02

Ragul

05:02 PM

No data where there

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

06:35 PM

Make sure the host:port/path is valid and outputs the metrics.

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 825 threads (61% resolved)

Join Our Community Manage subscription

Similar Threads

Monitoring JDBC and HIKARI Metrics in SigNoz

Ragulraj is unable to monitor JDBC and HIKARI metrics in their spring boot application using SigNoz. Srikanth suggests configuring `scrape_configs` in `otel-collector-metrics`.

Unable to Monitor jdbc_connections_active Metrics in SigNoz

Ragulraj is unable to monitor jdbc_connections_active metrics with SigNoz despite modifying configurations and adding dependencies. Srikanth provided troubleshooting steps and info on alternatives, but the issue remains unresolved.

Issues with SigNoz Setup and Data Persistence in AKS

Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.

Configuring Signoz to Consume Metrics From App's Endpoint

Sindhu wanted to configure Signoz to consume metrics from their app's endpoint. Ankit provided guidance on enabling a Prometheus receiver and suggested changing the host path for Docker.

Extracting Custom Fields as Attributes from Log in SigNoz

Harald wants to have custom fields from their body parsed as attributes in the SigNoz logger. They have tried implementing suggestions from nitya-signoz and Prashant, but the issue remains unsolved due to a potential race condition encountered while executing the code. They have provided a full example using Kind for further assistance.

Powered By