https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
r
Hi George 🙂 There doesn't seem to be anything wrong with your config. Is "accounts.midcloud.app" reachable from your collector instance? Your collector logs should contain more details. Please take a look at them and if you don't mind please share the logs with us
g
it is reachable, even publicly, i am stressed
is the job_name supposed to be arbitrary or should it be a specific value? Or else how do I specify the otel exporter ?
can someone please help me with this, I have been battling this issue for 2 days
r
You should be able to use any job_name you like - see https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config for more details around prometheus config
Please share your collector logs with us. We can not help much without seeing some logs
s
What is the port where metrics are being exported? Do you see any error logs with failed scrape message?
r
Metrics are being exported to where the config points based on prometheus defaults - https://accounts.midcloud.app/metrics
@George James apart from sharing collector logs, please try using the following updated config to ensure you are using that receiver in some collector pipeline
Copy code
otelCollector:
  config:
    receivers:
      prometheus:
        config:
          scrape_configs:
            - job_name: keycloak
              scheme: https
              scrape_interval: 15s
              static_configs:
                - targets: ["<http://accounts.midcloud.app|accounts.midcloud.app>"]
    service:
      pipelines:
        metrics/prom:
          receivers: [prometheus]
          processors: [batch]
          exporters: [clickhousemetricswrite]
g
@Raj Kamal that configuration worked for me. Is there somewhere where this is documented ?
r
great! So you had updated the config to define a new receiver for collecting prometheus metrics, but receivers need to be used in a collector pipeline for them to actually get used. I would highly recommend that you should go through https://opentelemetry.io/docs/collector/configuration/ to understand the details of working with otel collector configuration
17 Views
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