Implementing Nginx Opentracing into SigNoz

Hi Everyone!

Has anyone successfully instrumented nginx opentracing into signoz?



nginx-config:

  opentracing: 'True'
  opentracing-tracer: /usr/local/lib/libjaegertracing_plugin.so
  opentracing-tracer-config: |
    {
      "service_name": "nginx-ingress",
      "sampler": {
        "type": "const",
        "param": 1
      },
      "reporter": {
        "localAgentHostPort": "otel-collector.opentelemetry-operator-system:14250"
      }
    }

otel-collector:

          ports:
            - containerPort: 55679
              protocol: TCP
            - containerPort: 4317
              protocol: TCP
            - containerPort: 14250
              protocol: TCP
            - containerPort: 14268
              protocol: TCP
            - containerPort: 9411
              protocol: TCP
            - containerPort: 8888
              protocol: TCP

otel-collector-config:

    receivers:
      otlp:
        protocols:
          grpc:
          http:
      jaeger:
        protocols:
          grpc:
            endpoint: 0.0.0.0:14250
          thrift_http:
            endpoint: 0.0.0.0:14268    

Also in otel-collector-config further down:

      pipelines:
        traces/1:
          receivers: 
          - otlp
          - jaeger

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:

"otel-collector.opentelemetry-operator-system:14250"

and also

"otel-collector.opentelemetry-operator-system:14268"

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 orjaeger.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.