TLDR Al is trying to implement nginx opentracing into SigNoz but encounters issues. Srikanth suggests exploring OpenTelemetry support for nginx instead.
Has anyone successfully instrumented into signoz?
``` opentracing: 'True'
- containerPort: 55679
- containerPort: 4317
- containerPort: 14250
- containerPort: 14268
- containerPort: 9411
- containerPort: 8888
endpoint: 0.0.0.0:14268 ```
Also in `otel-collector-config` further down:
Not sure what I'm missing, thanks!!
Have you managed to find anything?
Hi Srikanth Thanks for checking in. No luck yet.
We have tried the following.
In `nginx-config`, we have tried using:
We have confirmed that `/usr/local/lib/libjaegertracing_plugin.so` exists.
I think we need to troubleshoot nginx and whether it is in fact initializing the `opentracing-tracer-config` I do not see anything in the nginx logs that indicates that tracing initialized.
It would also be good to confirm whether `jaeger.protocols.grpc` or`jaeger.protocols.thrift_http` connections are being received at the `otel-collector`
The collector itself doesn’t provide any connection related metrics as of now. There is also OpenTelemetry support for nginx so may be try using the OTLP receiver directly instead of relying on OpenTracing+Jaeger endpoint.
Thanks. We'll look into OpenTelemetry support for nginx and report back.
Indexed 1060 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI