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`.
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 . 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
What does your scrape config look like? There is probably some n/w issue while scraping.
scrape config is default one from helm values.yaml . i have not did any changes
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.
i should add promethus config in values.yaml ?
if yes , please help me in overiding the values.yaml
Yes, you need to add an additional scrape config in values.yaml. It would look like following.
# prometheus scrape config
- job_name: 'applications-metrics'
metrics_path: <your probe endpoint>
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
for cross check in signoz clickhouse i tried with -> SELECT name
SELECT DISTINCT JSONExtractString(labels, '__name__') AS name
) AS tmp1
WHERE name ILIKE '%jdbc%' with this query
No data where there
Make sure the `host:port/path` is valid and outputs the metrics.
Indexed 1061 threads
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