datalust / datalust/seq-extensions-logging
Capture `System.Text.Json` documents directly as structured data
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 99
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
I'm using System.Text.Json.Serialization attributes/convertors for configuring serialization of my classes, but I think Seq logger is using Newtonsoft.Json so when I use the @ character to log an object like Logger.LogInformation("{@Item}", Item); it uses the default serialization all will include all [JsonIgnore] properties which makes the object very bloated and large. My request is to add an option in .AddSeq to be able to chose the serialization method between Newtonsoft and Microsoft's. I think more people will need this as more people use dotnet's JSON library for their new projects. Thanks!
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 configuration and the current Newtonsoft.Json path used for structured object logging. Determine how an option could select Microsoft's System.Text.Json while honoring its serialization attributes, then verify that both serialization choices produce the expected logged structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100