Skip to content

feat: Add option to exclude certain HTTP statuses from tracing #5034

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jamescrosswell wants to merge 13 commits into
base: main
Choose a base branch
from

Use collection operators from c# 12

e9e00d9
Select commit
Loading
Failed to load commit list.
Open

feat: Add option to exclude certain HTTP statuses from tracing #5034

Use collection operators from c# 12
e9e00d9
Select commit
Loading
Failed to load commit list.
@sentry/warden / warden completed Mar 18, 2026 in 5m 3s

1 issue

High

TraceIgnoreStatusCodeTransactionProcessor reads from unpopulated Data dictionary - `src/Sentry/Internal/TraceIgnoreStatusCodeTransactionProcessor.cs:22-24`

The processor reads transaction.Data.TryGetValue(OtelSemanticConventions.AttributeHttpResponseStatusCode, ...) which returns Contexts.Trace.Data. However, when transactions are created from TransactionTracer (the normal flow in ASP.NET Core), the HTTP status code set via SetExtra() is stored in TransactionTracer._data, not in TransactionTracer.Contexts.Trace.Data. The SentryTransaction(ITransactionTracer) constructor copies Contexts but never transfers tracer.Data to Contexts.Trace.Data. The feature will silently fail to filter transactions by status code.

4 skills analyzed
Skill Findings Duration Cost
code-review 0 1m 21s $1.66
find-bugs 1 4m 50s $7.21
gha-security-review 0 3m 43s $0.45
security-review 0 4m 37s $0.98

Duration: 14m 31s · Tokens: 9.2M in / 50.8k out · Cost: $10.31 (+extraction: $0.01, +dedup: $0.00)

View more details on @sentry/warden