feat: Add OpenTelemetry documentation #824
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds OpenTelemetry documentation for NGINX Ingress Controller, coverting an example hidden in the code repository. It adds it to the "Logging and monitoring" section, where the prior OpenTracing document has also been moved. The latter document has had an explicit warning call-out added to the top directing users to the new document, and the release page now links directly to the new configuration document for context. Some page titles and metadata in the section have also been updated as part of this work, to ensure the user experience is more consistent.
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
y82
approved these changes
Jul 17, 2025
vepatel
reviewed
Jul 17, 2025
Co-authored-by: yar <y82@users.noreply.github.com>
ADubhlaoich
force-pushed
the
nic/otel-instructions
branch
from
37e4e16 to
c4e8ec4
Compare
ADubhlaoich
added a commit
to nginx/kubernetes-ingress
that referenced
this pull request
Jul 17, 2025
This commit replaces the example text for OpenTelemetry with the production website URL, creating one single source of truth for instruction in a place more easily discoverable to users. It is follow-up work from the documentation PR: nginx/documentation#824
6 tasks
vepatel
reviewed
Jul 17, 2025
vepatel
approved these changes
Jul 18, 2025
AlexFenlon
approved these changes
Jul 18, 2025
ADubhlaoich
added a commit
to nginx/kubernetes-ingress
that referenced
this pull request
Jul 18, 2025
This commit replaces the example text for OpenTelemetry with the production website URL, creating one single source of truth for instruction in a place more easily discoverable to users. It is follow-up work from the documentation PR: nginx/documentation#824 --------- Co-authored-by: Venktesh Shivam Patel <ve.patel@f5.com>
github-actions bot
pushed a commit
to nginx/kubernetes-ingress
that referenced
this pull request
Jul 18, 2025
This commit replaces the example text for OpenTelemetry with the production website URL, creating one single source of truth for instruction in a place more easily discoverable to users. It is follow-up work from the documentation PR: nginx/documentation#824 --------- Co-authored-by: Venktesh Shivam Patel <ve.patel@f5.com>
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
This pull request adds OpenTelemetry documentation for NGINX Ingress Controller, converting an example hidden in the code repository. It adds it to the "Logging and monitoring" section, where the prior OpenTracing document has also been moved.
The latter document has had an explicit warning call-out added to the top directing users to the new document, and the release page now links directly to the new configuration document for context.
Some page titles and metadata in the section have also been updated as part of this work, to ensure the user experience is more consistent.
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.mdFootnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩