Extend Forwarder to accept the legacy "raw" event format
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 167
- Forks
- 30
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 9
Description
We have been trying to update a older forwarder (https://github.com/datalust/seq-forwarder) to the new seqcli recomendation (https://github.com/datalust/seq-forwarder/issues/54#issuecomment-3111652999) but all the raw messages are not working.
"seqcli forwarder" only works with "--pre". But the "--pre" also disables raw messages.
Older serilog clients will keep sending messages as raw.
2026-02-02T16:21:38.8534132Z [16:21:38 ERR] Client supplied a legacy raw-format (non-CLEF) payload
Contributor guide
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
The report concerns the seqcli forwarder path and its --pre/raw-message handling; start there and compare it with the legacy raw-format failure described in the issue. Done means older Serilog clients can send raw events without requiring --pre, while the current forwarding behavior remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100