MartinLam12 opened a new pull request, #10900:
URL: https://github.com/apache/seatunnel/pull/10900
## Purpose
Closes #2649
Adds a new `Syslog` source connector that receives syslog messages over TCP
and parses them according to RFC 3164 (BSD syslog format).
## What's Included
- **connector-syslog** module under `seatunnel-connectors-v2/`
- RFC 3164 parser that extracts structured fields from each message
- Registered in `plugin-mapping.properties` and `seatunnel-dist`
- Unit tests covering standard messages, PID parsing, single-digit day
padding, and malformed input
- English and Chinese documentation
## Output Schema
Each syslog message is parsed into 7 columns:
| Column | Type | Description |
|---|---|---|
| facility | INT | Facility code (0–23) derived from PRI field |
| severity | INT | Severity level (0–7) derived from PRI field |
| timestamp | STRING | Raw timestamp from the message |
| hostname | STRING | Originating host |
| app_name | STRING | Application/process name from TAG field |
| proc_id | STRING | Process ID from TAG field, empty if absent |
| message | STRING | Log message content |
## Scope (Phase 1)
- Protocol: **TCP only**
- Format: **RFC 3164** (BSD syslog)
- Transport: connector acts as a **server**, listening on a configured port
- Output: **parsed fields** (not raw string)
UDP and RFC 5424 support are deferred to a future phase.
## Example Config
```hocon
source {
Syslog {
port = 514
host = "0.0.0.0"
}
}
```
## Checklist
- [x] Spotless formatting applied (`./mvnw spotless:apply`)
- [x] Module compiles cleanly (`./mvnw -q -DskipTests verify`)
- [x] Unit tests written
- [x] `plugin-mapping.properties` updated
- [x] `seatunnel-dist/pom.xml` updated
- [x] Documentation added in `docs/en` and `docs/zh`
- [x] Apache license header on all new files
- [x] No new external dependencies introduced
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
