https://signoz.io logo
Join Slack
Powered by
Hi guys, hope this is the right place to ask, is t...
# support
m
Hi guys, hope this is the right place to ask, is there a documentation of how to migrate from jaeger for tracing and prometheus for metrics to signoz? my installation is on AKS (Azure)
s
Yes, what is the instrumentation library did you to instrument your code?
The default SigNoz install already enabled the jaeger receiver i.e you can configure you application to send data directly https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/otel-collector-config.yaml#L39.
For metrics, you need have to configure the scrape jobs for you application here https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/otel-collector-metrics-config.yaml#L8
Are you running kubernetes?
m
yes, AKS with instrumentation lib opentemetry go SDK
s
Oh then you don’t need any jaeger receiver. You can send OTLP directly to SigNoz. What is the metrics instrumentation library?
m
Azure Kubernetes service
s
How is your metrics instrumentation done?
m
we are using prometheus with grafana
and elasticsearch for logs
s
I was interested in the instrumentation library; which client library are you using for metrics? Is it OTEL, OpenCensus, Prometheus native go client or something else etc…?
m
opentemetry
its OTEL i guess
s
You can send both directly over OTLP. All you need to do is configure the SDK with OTLPExporter pointing to SigNoz endpoint.
m
will try it, thank you!
can I connect it to the existing jaeger without changing code configuration?
s
I didn’t get it. what do you want to connect to the existing jaeger?
m
sorry if i'm not clear, i want to connect to it to existing collector, and run it side by side to the existing jaeger installation
s
You can configure the SDK to directly send to multiple destinations i.e multiple exporters one for SigNoz collector and other for Jaeger.
4 Views
Open in Slack
PreviousNext
Powered by