Implement OpenTelemetry tracing #4169
brianehlert
started this conversation in
Ideas
Replies: 2 comments 2 replies
-
The NGINX OTEL module mentioned above is currently exclusive to NGINX Plus (unfortunately) and does not meet the needs of our NGINX OSS user base. We will re-evaluate this as we don't want to implement different solutions for the paid and free edition. |
Beta Was this translation helpful? Give feedback.
2 replies
-
do you have any article to run this with grafana? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The NGINX team recently released a native OpenTelemetry tracing module: https://nginx.org/en/docs/ngx_otel_module.html
This finally allows the NGINX Ingress Controller to implement OpenTelemetry tracing and set a deprecation path for the currently included OpenTracing module.
There will be a period of time where both modules should be present in the images so that users have a chance to do in place upgrades through modifying their resources and converting to the opentelemetry tracing configuration.
If we followed the 'normal' K8s API deprecation process this would be three releases of compatibility where both modules would be present. Following the current quarterly release practices, this would be an overlap period 9 months.
For example: opentracing only -> opentracing / open telemetry -> opentracing / open telemetry -> opentracing / open telemetry -> open telemetry only
We don't know how many customers implement OpenTracing today and thus are unsure of the real impact, but estimate that 9 months should give adequate planning and modification time.
Also, considering the number of times that OpenTelemetry adoption has been raised, we are unclear if any users have tools that do not support OpenTelemetry where removing OpenTracting would be considered a burden.
Beta Was this translation helpful? Give feedback.
All reactions