Distributed tracing implementation docs and guides#745
Merged
Conversation
Collaborator
Author
zdtsw
reviewed
Feb 23, 2026
6e3eaef to
21fa3ff
Compare
24 tasks
b9b951d to
2cd9877
Compare
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: sallyom <somalley@redhat.com>
Route all tracing through an OTel Collector instead of exporting directly to Jaeger. The new install script deploys both the collector and Jaeger into the user-specified namespace (-n required). It auto-detects the OpenTelemetry Operator CRD and uses an OpenTelemetryCollector CR when available, falling back to a standalone Deployment otherwise. Both paths produce the same service name (otel-collector) so all chart defaults use the short name http://otel-collector:4317, resolving within the workload namespace with no cross-namespace references. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: sallyom <somalley@redhat.com>
Signed-off-by: sallyom <somalley@redhat.com>
Signed-off-by: sallyom <somalley@redhat.com>
2cd9877 to
2084417
Compare
diegocastanibm
pushed a commit
to diegocastanibm/llm-d
that referenced
this pull request
Mar 18, 2026
* Add tracing config to all GAIE guide values Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: sallyom <somalley@redhat.com> * docs: replace install-jaeger.sh with install-otel-collector-jaeger.sh Route all tracing through an OTel Collector instead of exporting directly to Jaeger. The new install script deploys both the collector and Jaeger into the user-specified namespace (-n required). It auto-detects the OpenTelemetry Operator CRD and uses an OpenTelemetryCollector CR when available, falling back to a standalone Deployment otherwise. Both paths produce the same service name (otel-collector) so all chart defaults use the short name http://otel-collector:4317, resolving within the workload namespace with no cross-namespace references. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: sallyom <somalley@redhat.com> * add tracing to new guides and clean up/update tracing README Signed-off-by: sallyom <somalley@redhat.com> * update promql queries Signed-off-by: sallyom <somalley@redhat.com> --------- Signed-off-by: sallyom <somalley@redhat.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
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
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.


Everything required to enable tracing is here!!
Also adding an install-otel-jaeger script, meant to install in the same ns where you are running your llm-d components.
Also adding cleanup to the generate-traffic scripts, adding one for pd specifically, and also dashboard for pd
Must accompany the following for complete implementation: