Open BrendanGalloway opened 1 year ago
Hello, what is the status of this issue ?
I have the same problem with Nginx 1.22.0 and OpenTelemetry Nginx module v1.0.3.
It doesnt recognize the opentelemetry_*
instructions:
unknown directive "opentelemetry_config" in /etc/nginx/nginx.conf:73
I am facing the same issue. Followed https://github.com/open-telemetry/opentelemetry-cpp-contrib/blob/main/instrumentation/nginx/README.md.
Neither opentelemetry_propagate
nor opentelemetry_attribute
are recognized.
OpenTelemetry module is otherwise working and sending traces to the oltp enpoints for collection.
Same issue with "unknown directive" opentelemetry_operationname ; opentelemetry_propagate; https://opentelemetry.io/blog/2022/instrument-nginx/
Same issue with "unknown directive"
Update: I have found the nginx official module that are more optimized (they say that not me) And it work very well : http://nginx.org/en/docs/ngx_otel_module.html
Describe your environment
Running nginx in a kubernetes pod to serve static content and proxy dynamic requests.
Steps to reproduce
Nginx pod was build with this dockerfile:
adding in static content is probably not necessary to reproduce.
nginx.conf, otel-nginx.toml and also opentelemetry_module.conf are loaded into the pod via configmap:
and the nginx.conf file is templated with the varnish and nginx version values before nginx starts.
What is the expected behavior? Nginx starts correctly and sends traces to the otel collector
What is the actual behavior?
nginx crashes with the message:
Additional context
I have also tried using the instructions in the opentelemetry blog which configure the module using
include /etc/nginx/config.d/*.conf
instead of theopentelemetry_config
directive. In that case nginx starts up and I see the error I describe in !255. Traces appear in Jaeger, but seemingly without propagation configured. If I try add opentelemetry directives, such asopentelemetry_propogation
oropentelemetry_trust_upstream_traces
, nginx crashes as described above