https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
s
What does your scrape config look like? There is probably some n/w issue while scraping.
r
scrape config is default one from helm values.yaml . i have not did any changes
s
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.
r
OK
if yes , please help me in overiding the values.yaml
s
Yes, you need to add an additional scrape config in values.yaml. It would look like following.
Copy code
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:
r
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 FROM ( SELECT DISTINCT JSONExtractString(labels, '__name__') AS name FROM signoz_metrics.time_series_v2 ) AS tmp1 WHERE name ILIKE '%jdbc%' with this query
No data where there
s
Make sure the 
host:port/path
is valid and outputs the metrics.
Open in Slack
PreviousNext
Powered by

SigNoz Community

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

Powered by