Hello, I'm running SigNoz in a local kind cluster ...
# support
e
Hello, I'm running SigNoz in a local kind cluster and using a Prometheus receiver to scrape metrics from the metrics endpoint of a locally running app. If this app is already running and producing metrics, SigNoz will display the metric name but provide no associated data. I'm able to see the metrics correctly in Prometheus however. Any thoughts on what could be wrong?
e
Did you configure the signoz otel collector to scrape that metrics endpoint?
Copy code
otelCollector:
       config:
         receivers:
           prometheus:
             config:
               global:
                 scrape_interval: 30s # Adjust this interval as needed
               # need 1 scape config per monitored cluster
               # each job is executed in parallel and the targets inside them are executed serially
               scrape_configs:
                 # monitor dev
                 - job_name: 'my-job'
                   static_configs:
                     - targets: ['prometheus_service_name:metrics_port']
                       labels:
                         customer: dev
         service:
           pipelines:
             metrics:
               receivers: [otlp, prometheus]
               processors: [batch]
               exporters: [clickhousemetricswrite]
e
Yes, I have that setup (though I'm running an app locally rather than as a service). It's interesting, because if I start up the app after SigNoz, I can collect all metrics. It's only if I start of SigNoz after the app has already been running and collecting metrics that SigNoz does not seem to scrape them correctly.