Al
05/10/2023, 10:08 PMopentracing: '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!!Srikanth Chekuri
05/12/2023, 8:13 AMAl
05/12/2023, 8:05 PMnginx-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
or`jaeger.protocols.thrift_http` connections are being received at the otel-collector
Srikanth Chekuri
05/15/2023, 6:48 AMAl
05/23/2023, 1:56 PM