rsyslog-doc
rsyslog-doc copied to clipboard
rsyslog
documentation for the rsyslog project
JSON is trendy. There is more chance that people have heard about JSON than rsyslog. After some digging I found some json-features in rsyslog. This is cool, because it allows...
http://www.rsyslog.com/doc/v8-devel/configuration/global/options/rsconf1_repeatedmsgreduction.html I think this defaults to off, but the page doesn't make that clear. This is really something that breaks a lot of log processing and so should be discouraged...
I am missing information about the `imdiag` module. It isn't listed in http://www.rsyslog.com/doc/v7-stable/configuration/modules.html or somewhere else or did I miss something?
Brought up by @davidelang and makes a lot of sense.
We need to define a standard way of describing a parameter. This is already inconsistent in the the original html doc and was on the "this needs to be fixed"...
Thanks to Björn Pettersson for letting us know about the problem.
**DO NOT MERGE** - this currently contains multiple proposed versions. For new users, clean up the language on when to use which format.
I see it's referred as `RSyslog`, `Rsyslog` and `rsyslog` on the [official site](https://rsyslog.com). It'd be nice to use a single style of naming everywhere.
In the [$DropTrailingLFOnReception](https://www.rsyslog.com/doc/configuration/input_directives/rsconf1_droptrailinglfonreception.html) documentation the sample is "$DropTrailingLFOnRecption on", it looks like an 'e' is missing from Reception.
