datalust / datalust/seq-extensions-logging
add a feature to disable seq sink logging at runtime after AddSeq has been called
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 99
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Abstract: the maui app I'm working on uses a settings file loaded at runtime which should be able to switch on seq logging only for specific users.
But currently AddSeq creates everything internally, including the SerilogLoggerProvider and its ControlledLevelSwitch that could make that feature work.
Could you improve that ?
Ty !
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the AddSeq entry point and how it creates SerilogLoggerProvider and ControlledLevelSwitch. Determine how the existing switch can be exposed or controlled after AddSeq returns, then verify that runtime settings can enable or disable Seq logging for selected users without recreating the logging setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100