feat(chart): configure OTLP export per signal - #37
Merged
EItanya merged 1 commit intoSep 11, 2026
Conversation
EItanya
approved these changes
Sep 11, 2026
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
2 participants
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.
Adds
otel.traces/otel.metrics/otel.logsto the chart so each signal can get its own OTLP endpoint (or be switched off), following the OTel SDK env var spec. Setting onlyotel.endpointrenders the same as before, plus the sampler env vars.Main use case today is send the router access log to a different collector than traces. Note that
traces.enabled/metrics.enabledonly affect agentgateway for now (and there's no metrics otlp push today), the Go components don't readOTEL_<SIGNAL>_EXPORTERyet (documented in values.yaml and the README).