Support logging internal metrics from `seqcli forwarder` to a secondary Seq instance
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 167
- Forks
- 30
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 9
Description
Forwarder can be tricky to manage: in particular, it's hard to tell when a forwarder instance has gone offline.
We should:
Adddone!diagnostics.internalLogServerUriand an API key setting that will turn on diagnostic logging to Seq- Periodically log metrics showing ingest rate, forwarding rate, and various errors
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
Start at the seqcli forwarder entry point and inspect the existing diagnostic logging settings, noting that the logging destination and API key work is marked done. Determine where ingest, forwarding, and error activity are available, then verify that periodic logs report all three metric categories to the secondary Seq instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100