Skip to content

Match OpenTelemetry probe exclusions to exact endpoints - #461

Merged
lesnik512 merged 1 commit into
mainfrom
fix/exact-otel-probe-exclusions
Nov 15, 2026
Merged

lesnik512 merged 1 commit into
mainfrom
fix/exact-otel-probe-exclusions

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Generated OpenTelemetry exclusions currently suppress application routes such as /health/details and /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.

@lesnik512
lesnik512 merged commit 3423480 into main Nov 15, 2026
35 checks passed
@lesnik512
lesnik512 deleted the fix/exact-otel-probe-exclusions branch November 15, 2026 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[P2] Match generated OTel probe exclusions to exact endpoints

1 participant