influxdata/telegraf

Syslog for agent logtarget

Open

#16,732 opened on Apr 7, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (9,892 stars) (4,161 forks)batch import
feature requesthelp wantedsize/m

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

Tech stack
go
Domain
observability
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingTelegraf codebase structuresyslog protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
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.
Syslog for agent logtarget · influxdata/telegraf#16732 | Good First Issue