This message was deleted.
# general
s
This message was deleted.
b
You can't use Signoz without opentelemetry in some way shape or form
r
I wonder what they meant by
Copy code
If you have a running Prometheus instance, and you expose metrics in Prometheus, then you can scrape them in SigNoz by configuring Prometheus receivers in the
b
Prometheus receiver inside of the opentelemetry collector
p
thanks @Blake Romano for the accurate answers 🙂 and helping out Raghu
r
thanks @Blake Romano My understanding is that opentelemetry collector is part of signoz installation. so what do we expect from application developers here? we have prometheus installed in our k8s cluster which is already scraping all targets. and my guess was that signoz would get those metrics.
I am trying to understand how can I integrate signoz without doing much development effort on our application
p
@Raghu I think you must be exposing those scraped prometheus metrics on some endpoint. You can just set those end points as targets for scraping in otel collector shipped with SigNoz. This section which you already link should be able to guide you - https://signoz.io/docs/userguide/send-metrics/#enable-a-prometheus-receiver
p
If you have exporters in the same K8s cluster as SigNoz, you could scrape metrics from them using
<http://signoz.io/scrape|signoz.io/scrape>
and
<http://signoz.io/port|signoz.io/port>
pod annotations. You will not need to update OtelCollectorMetrics config nor any external prometheus instance.
r
Thanks @Pranay @Prashant Shahi. Do you have a sample config that I can use to test these options. I would want to get a working setup that I can demo to our team.
p
If you need complete sample to test it, we don't have anything independent yet. However, we enable metrics scraping by default for Clickhouse metrics and OtelCollector's internal metrics.