-
### Component(s)
exporter/syslog
### What happened?
## Description
In the case when you have several fields in the "attributes.structured_data" object, the resulting syslog entry will not be for…
-
### Is your feature request related to a problem? Please describe.
Grabbing log messages from the web UI is cumbersome and I'd like to have a continuously running log sink.
### Describe the solution…
ranma updated
12 hours ago
-
(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…
-
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.
-
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…
-
**Describe the enhancement:**
Filebeat syslog input module doesn't support RFC5424 time format "1985-04-12T23:20:50.52Z" or "1985-04-12T19:20:50.52-04:00" which are present in RFC5424 examples http…