-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update syslog input plugin #7023
Comments
Thanks Leo! Is this update you would like to work on or would you rather we handle it? |
Hey @danielnelson! At the moment, I don't think to have time to handle it so it depends on you folks! |
Is there a work around to this? I'm assuming this would be why my network gear and Solarwinds Log Forwarders for windows are failing? Anything using Rsyslog is working correctly but all items using Syslog clients directly to the Telegraf Instance are getting the errors below. Telegraf v1.13.4 UDP Client |
The best workaround is to use rsyslog to convert to the RFC5424 format. If you are feeling adventurous you should be able to send RFC3164 directly to the |
Nope :) Ty! |
Feature Request
Hello folks! 🤗
I'm opening this issue to notify y'all that some days ago I finally completed a (first, initial) parser for BSD-syslog messages (see rfc3164). My friend @goller then released v3 for go-syslog to include it.
This issue is to request that the syslog input plugin gets updated to go-syslog v3.
Proposal:
3.1 Take into account the various parsing options it provides
Current behavior:
Depending on go-syslog v2.
Supporting RFC5424 parsing, with octect-counting or with non-transparent framing technique.
Desired behavior:
Depending on go-syslog v3.
Supporting RFC3164 parsing (with tunable options), too.
Use case:
Should unblock (at least, partially, depending on the "kind" of BSD-syslog messages people wants to parse) issue #4593 - Blocking #4593
Also refs to #4902
The text was updated successfully, but these errors were encountered: