influxdata / influxdata/telegraf
Syslog for agent logtarget
- Dominant language
- Go
- Stars
- 17.8k
- Forks
- 5.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 161
Description
### Use Case
Currently Telegraf can not write its own log to syslog. Syslog is a standard solution for log collection on many *nix systems.
### Expected behavior
I can specify syslog as agent logtarget and collect log lines in my syslog server.
### Actual behavior
Well, Telegraf doesn't provide such an option.
### Additional info
_No response_
Contributor guide
Research direction
No files, tests, or entry points are named in the issue. Start by locating Telegraf's agent logtarget configuration and current logging implementation, then determine how a syslog target would be configured and validated. Done means an agent can select syslog and its log lines reach a syslog server, with coverage for the new behavior.
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