-
Logs generated for RFC5424 only compliant about 40% of the time.
Sample set of 100 logs generated with `flog`: https://regex101.com/r/nMlGtT/1
Testing using the Fluent Bit [syslog-rfc5424 parse…
-
(This issue was originally filed by @suyograo at https://github.com/elastic/logstash/issues/1667)
---
Logstash has the [syslog input](http://logstash.net/docs/1.4.2/inputs/syslog) which only support…
-
I'd like to use this container as a bridge to send only rfc5424 to telegraf (influxdb) container.
Is it possible? In the environment I only see I can specify the host and the port but not the forma…
-
LS provides separate RFC5424 grok parsers[1], meaning conditional support is needed for that, in conjunction with necessary field normalization.
[1] https://github.com/logstash-plugins/logstash-pat…
-
The new Cisco IOS-XE devices have an option to send syslog using RFC5424 with command "logging trap syslog-format rfc5424"
I'm sending syslogs directly to promtail and can see them in Loki etc but …
-
Hi,
the logs from vmware are incorrectly detected as RFC5425.
vmvware is sending messages like this:
**2**016-01-29T15:20:31.960Z srv01esx70 Vpxa: [FF8DFB70 verbose 'VpxaHalCnxHostagent' opID=WFU-ba7…
-
Examples of lines which are not parsed correctly:
```
full_message
1 2018-03-25T22:14:15.003Z mymachine.example.com su - ID47 - 'su root' failed for lonvick on /dev/pts/8
---
full_message
1 2018…
-
In a test of this plugin I found the timeQuality (RFC5424, Section 7.1) part of the message not being parsed.
Would be nice if it gets added to the parser.
-
Currently `loki.source.syslog` only supports RFC5424 formatted messages. In #305 the issue is raised that RFC-3164 formatted messages lead to an error. PR #1556 was opened to address this with RFC-316…
-
Continuing the work started in #3377
Address these firewall integrations to ensure each is consistent in the syslog formats supported.
**Fortinet**
Syslog configuration now includes the optio…