influxdata/telegraf

Syslog for agent logtarget

Open

#16,732 建立於 2025年4月7日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Go (9,892 star) (4,161 fork)batch import
feature requesthelp wantedsize/m

描述

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

貢獻者指南

技術棧
go
領域
observability
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programmingTelegraf codebase structuresyslog protocol
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
Research Telegraf's logging implementation, likely in the `internal/` directory, to understand how log targets are currently configured (e.g., file, stderr). Add a new log target for syslog using Go's `log/syslog` package. Modify the configuration parsing to accept 'syslog' as a valid logtarget value. Consider following the pattern of existing log writers. There are no linked PRs or comments with specific file paths.