Repository navigation
Match OpenTelemetry probe exclusions to exact endpoints - #461
Merged
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
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.
Generated OpenTelemetry exclusions currently suppress application routes such as
/health/detailsand/metrics/report, while a health endpoint at/is still traced. Match each configured endpoint and its single trailing-slash variant exactly, including root health checks.The shared FastAPI/FastMCP wrapper uses an explicit path set, and Litestar uses fully anchored patterns. Exporter regressions cover FastAPI and Litestar with proxy prefixes, caller regexes, and a distinct
/health//route. The 2.x migration guide documents the trace inclusion change.Closes #453.
All 677 tests passed with 100% line coverage. Type checking, Ruff, the strict docs build, and standards and spec reviews passed.