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.
RSyslog Windows Agent 6.0 Released
Release Date: 2019-07-01
Build-IDs: Service 6.0.0.200, Client 6.0.0.277
Features |
|
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
RSyslog Windows Agent 6.0 Released
We are proud to announce the next major release of Rsyslog Windows Agent, version 6.
Most importantly this version fully supports Windows Server 2019, enhanced cross-platform and mass deployment
support as well as provides even better performance.
Windows Server 2019 is becoming main-stream in many data centers. The new version now fully
supports the new Windows including all updated libraries. Native JSON expression of Windows Event
Log data enables easy integration into many other solutions. The configuration can now
automatically be updated from a central configuration repository. This option is very useful for large
deployments, especially with remote sites. Performance has even more been tuned all over the
product, with huge wins inside the Event Log Monitor service.
RSyslog Windows Agent 5.2 Released
Release Date: 2019-04-25
Build-IDs: Service 5.2.0.195, Client 5.2.0.274
Features |
|
Bugfixes |
|
You can download Free Trial Version of RSyslog Windows Agent.
