-
Checked on syslog-ng 3.17.2 (that is available in NetBSD pkgsrc), so it might be already fixed. NetBSD uses RFC5424 syslog, but the system() source for NetBSD uses legacy. And it does not collect kern…
-
### Expected behavior
Ability to have own container name instead of `rfc5424-sd`. E.g. like the `container` option for mmjsonparse.
### Actual behavior
The module hardcodes placing structured…
-
**Is your feature request related to a problem? Please describe.**
No.
**Describe the solution you'd like**
When receiving messages over the `/dev/log` unix socket, it would be quite easy for…
-
Consider the following code :
```js
const parser = require("nsyslog-parser");
console.log(parser('1 2021-05-06T08:02:30.282938Z host APP 1000 l [c q="x"]').structuredData);
console.log(parser('1 2…
-
## Suggestion
The given timestamp format is RFC5424, a subset of ISO8601
https://tools.ietf.org/html/rfc5424#section-6.2.3
A more liberal approach - though more restrictive than iso8601 - i…
-
We use syslog with structured logging according to rfc5424 in order to send our logmessages. Within our layout we use the `${all-event-properties}` layout renderer. One of the values provided to a pro…
-
https://tools.ietf.org/html/rfc5424. Support for structured data will be very helpful.
-
Create a new syslog codec to add support for [RFC3164](https://tools.ietf.org/html/rfc3164) and [RFC5424](https://tools.ietf.org/html/rfc5424) (with continued ISO8601 date format support) so it can be…
-
when logging via imuxsock a RFC5424 formatted message
```
logger --rfc5424 "hello"
```
One would expect the message to be parsed. Instead, the header is handled as message data, for example :
Dec…
-
https://github.com/influxdata/go-syslog/blob/ac565dc76ba6bb17b47140fb74355d1de7f19307/rfc5424/builder.go#L64-L65
Those two variables are defined on the package level. That means that two independen…