influxdata / influxdata/kapacitor
Log to syslog
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
It would be nice if kapacitor could log to syslog instead of just files or STDOUT/STDERR.
The current STDOUT logging poses a problem on systemd because of a limitation where journald splits lines at 2k chars (https://bugs.freedesktop.org/show_bug.cgi?id=86465). When using `|log()` statements to debug a script, these lines can easily exceed 2k, and thus get split up, making parsing rather difficult.
Messages logged through the syslog socket do not have this 2k limitation. I'm not sure what the limitation is for the max length of a syslog message, but It's > 16k.
Contributor guide
Research direction
Search the repository for the existing file and STDOUT/STDERR logging implementation, then trace how logging destinations are configured. Determine how a syslog destination should be selected and verify that long log messages are delivered without the stated journald line-splitting problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100