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.