RSyslog Windows Agent 6.2b Released
We are proud to announce the 6.2b release of Rsyslog Windows Agent.
This is a bugfixing release with fixes for the “Start Program Action” and a buffer overrun in the queue engine.
RSyslog Windows Agent 6.2b Released
Release Date: 2020-09-04
Build-IDs: Service 6.2.0.209, Client 6.2.0.284
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 6.2a Released
We are proud to announce the 6.2a release of Rsyslog Windows Agent.
This is a minor update for the last maintenance release of this major
Version. A problem was solved that happened when the user stopped the
service while a configuration reload was active. Detailed information can
be found in the version history.
RSyslog Windows Agent 6.2a Released
Release Date: 2020-07-21
Build-IDs: Service 6.2.0.208, Client 6.2.0.284
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 6.2 Released
Release Date: 2020-06-16
Build-IDs: Service 6.2.0.207, Client 6.2.0.284
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 6.2 Released
We are proud to announce the 6.2 release of Rsyslog Windows Agent.
This is a maintenance release and properly the last for this major
Version. We have hardened the Service code further and fixed multiple
minor bugs.
RSyslog Windows Agent 6.1a Released
Release Date: 2020-03-10
Build-IDs: Service 6.1.0.206, Client 6.1.0.280
Features |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 6.1 Released
Release Date: 2020-01-31
Build-IDs: Service 6.1.0.205, Client 6.1.0.280
Features |
|
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 6.1 Released
We are proud to announce the 6.1 release of Rsyslog Windows Agent.
This is a maintenance release and properly the last for this major
Version. We have hardened the Service code further and fixed multiple
minor bugs.
Encasing of control structures
When using control structures to create some case filtering, there are some things to consider when formatting this.
In general, a control structure can be as simple as this:
if $msg contains "word" then
action()
else
action()While this is correct and will work as expected, it is generally better style to encase expressions and actions. That way, they are more clearly separated from the control structure itself for better overview and can be more easily expanded without error. When using multiple actions or expressions, encasing is needed anyway, so we think it’s good practice to always use it.
Example:
if ($msg contains "word") then {
action()
} else {
action()
}And a more complex example:
if ($msg contains "word" and $source == "123.123.123.123") then {
action()
action()
} else {
action()
action()
}All three sample snippets above are correct in their own way. Added complexity makes encasing necessary though. So, you may as well use it for all your filters to have a consistent and all-case proof configuration.
