sneak/simplelog
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

feat: add RELP handler for reliable log delivery to rsyslog (closes #5) #8

Closed
clawbot wants to merge 3 commits from feat/relp-handler into main
pull from: feat/relp-handler
merge into: sneak:main
Conversation 1 Commits 3 Files Changed 3 +346 -2
clawbot commented 2026-03-01 15:00:09 +01:00
Collaborator
Copy Link

Replaces PR #6 (which pulled from the clawbot fork). Branch is now repo-local.

Implements the planned RELP feature from the README.

What

  • New RELPHandler that delivers log messages to a remote rsyslog server via RELP (TCP)
  • Configured via LOGGER_RELP_URL env var (e.g. tcp://rsyslog.example.com:2514)
  • Pure Go implementation — no CGO, no librelp dependency

How it works

  • Lazy connection on first log message
  • RELP session: open handshake → syslog commands → graceful close
  • Per-message acknowledgement (waits for rsp 200 from server)
  • Auto-reconnect on connection failure
  • Messages formatted as RFC 5424 syslog with structured data from slog attributes
  • Transaction number tracking with proper wraparound at 999,999,999

Notes

  • Also includes the deadlock fix from #3 (cherry-picked) since it was needed as a clean base
  • No TLS support yet (could be added later via tls:// scheme)
  • Default port 2514 (standard RELP/imrelp port)

Closes #5

Replaces [PR #6](https://git.eeqj.de/sneak/simplelog/pulls/6) (which pulled from the clawbot fork). Branch is now repo-local. Implements the planned RELP feature from the README. ## What - New `RELPHandler` that delivers log messages to a remote rsyslog server via RELP (TCP) - Configured via `LOGGER_RELP_URL` env var (e.g. `tcp://rsyslog.example.com:2514`) - Pure Go implementation — no CGO, no librelp dependency ## How it works - Lazy connection on first log message - RELP session: `open` handshake → `syslog` commands → graceful `close` - Per-message acknowledgement (waits for `rsp 200` from server) - Auto-reconnect on connection failure - Messages formatted as RFC 5424 syslog with structured data from slog attributes - Transaction number tracking with proper wraparound at 999,999,999 ## Notes - Also includes the deadlock fix from #3 (cherry-picked) since it was needed as a clean base - No TLS support yet (could be added later via `tls://` scheme) - Default port 2514 (standard RELP/imrelp port) Closes #5
clawbot added 3 commits 2026-03-01 15:00:10 +01:00
sneak commented 2026-03-01 15:09:59 +01:00
Owner
Copy Link

tbh i think this is out of scope for simplelog. if we do do it, it should be with TLS support and the whole relp client should be pulled out into its own package. closing for now.

tbh i think this is out of scope for `simplelog`. if we do do it, it should be with TLS support and the whole relp client should be pulled out into its own package. closing for now.
sneak closed this pull request 2026-03-01 15:09:59 +01:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bot

Agent's turn to work

  
merge-ready

   
needs-checks

   
needs-rebase

   
needs-review

   
needs-rework
No Label
bot
merge-ready
needs-checks
needs-rebase
needs-review
needs-rework
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sneak/simplelog#8
No description provided.
Delete Branch "feat/relp-handler"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?