Open blotus opened 11 months ago
@blotus: Thanks for opening an issue, it is currently awaiting triage.
In the meantime, you can:
@blotus: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.
/kind feature
/kind enhancement
/kind bug
/kind packaging
The syslog acquisition modules tries to be a little bit too "smart" and reconstruct a RFC3164 syslog line based on what what read from the network.
But it fails often if your syslog messages are not fully compliant with either RFC3164 or RFC5424. In some cases, this totally prevent you from parsing the logs properly.
We should add a new configuration option in the syslog datasource to forward the message without trying to reconstruct the content after reading it from the network (but still after basic syslog parsing, such as the priority or any field that do not appear in the standard textual representation of a syslog message).