getsentry / getsentry/sentry-dotnet
DataCollection phase 2: migrate core enricher (UserInfo)
- Dominant language
- C#
- Stars
- 770
- Forks
- 248
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 51
Description
Part of #5420. Phase 2 — behavior-neutral consumer migration (via the SendDefaultPii bridge).
Gate core-SDK user info collection on resolved `UserInfo` instead of reading `SendDefaultPii` directly:
- `src/Sentry/Internal/Enricher.cs:85-93` — env username (`IsEnvironmentUser`), `User.IpAddress ??= "{{auto}}"`.
- `src/Sentry/Internal/MainSentryEventProcessor.cs:76-79` — `Environment.MachineName` as ServerName.
- `src/Sentry/SentryLog.cs:161-163` — `server.address` attribute on logs.
Explicitly user-set `User` data remains untouched (never gated).
Contributor guide
Research direction
Start with the listed ranges in src/Sentry/Internal/Enricher.cs, src/Sentry/Internal/MainSentryEventProcessor.cs, and src/Sentry/SentryLog.cs, then trace the SendDefaultPii bridge and resolved UserInfo behavior. Migrate only the automatic username, IP address, machine name, and log server address consumers; explicit user-set User data must remain ungated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100