feat(http): add --otlp-tracing-filter to exclude HTTP paths from Open…#887
Draft
bastiansmn wants to merge 1 commit into
Draft
feat(http): add --otlp-tracing-filter to exclude HTTP paths from Open…#887bastiansmn wants to merge 1 commit into
bastiansmn wants to merge 1 commit into
Conversation
…Telemetry tracing Health checks, metrics scrapes, and other probe endpoints generate noise in OpenTelemetry traces without revealing meaningful traffic patterns. The new --otlp-tracing-filter flag (repeatable, or comma-separated via env var) accepts a list of exact HTTP paths that should produce no OTEL span. Internally OtelAxumLayer.filter() is used so excluded paths emit tracing::Span::none() with zero overhead on the hot path.
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.
…Telemetry tracing
Health checks, metrics scrapes, and other probe endpoints generate noise in OpenTelemetry traces without revealing meaningful traffic patterns. The new --otlp-tracing-filter flag (repeatable, or comma-separated via env var) accepts a list of exact HTTP paths that should produce no OTEL span. Internally OtelAxumLayer.filter() is used so excluded paths emit tracing::Span::none() with zero overhead on the hot path.
What does this PR do?
Fixes # (issue)
Before submitting
instasnapshots?Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.