getsentry / getsentry/sentry-dotnet
DataCollection phase 1: config binding (appsettings)
- Dominant language
- C#
- Stars
- 770
- Forks
- 248
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 51
Description
Part of #5420. Phase 1 — foundation.
Make `DataCollection` configurable from `appsettings.json` / `IConfiguration` — a .NET-specific requirement the JS SDK didn't have.
- Mirror the shape in `src/Sentry/BindableSentryOptions.cs` (and `BindableSentryAspNetCoreOptions` if anything platform-specific lands there).
- `KeyValueCollectionBehavior` needs a config-friendly representation (e.g. `"Mode"` + `"Terms"` keys, or reuse of the `StringOrRegex` binding helper in `src/Sentry/StringOrRegex.cs:119` used by `TracePropagationTargets`).
- Wire through `src/Sentry.Extensions.Logging/SentryLoggingOptionsSetup.cs`.
- Tests for binding round-trips.
Contributor guide
Research direction
Start with src/Sentry/BindableSentryOptions.cs and inspect BindableSentryAspNetCoreOptions for platform-specific configuration. Read the StringOrRegex binding helper at src/Sentry/StringOrRegex.cs:119 and SentryLoggingOptionsSetup.cs to trace existing configuration wiring. Done means DataCollection binds from appsettings.json/IConfiguration and binding round-trip tests cover the supported representation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100