13 comments (13 comments)4 reactions (4 reactions)0 assignees (0 assignees)Go22,391 stars (22,391 stars)1,448 forks (1,448 forks)batch import
enhancementhelp wanted
Description
now zap can write to stderr and stdout...
Is any plan to support syslog?
Contributor guide
- Tech stack
- go
- Domain
- backend
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-2 days
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- clear
- Prerequisites
- Go programmingfamiliarity with zap loggingunderstanding of syslog
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 50
- Research direction
- Study the existing sink and encoder implementations in zap (e.g., zapcore.WriteSyncer, JSONEncoder, ConsoleEncoder) to understand the pattern. Review RFC 5424 for syslog message format. Look at comments in the issue for any prior attempts or guidance from maintainers. Implement a new SyslogEncoder and SyslogSink that formats log entries according to syslog and writes to /dev/log or via UDP/TCP.