Today, we release rsyslog 8.36.0.
The biggest enhancement is that rsyslog now provides support for opennssl for encryption in addition to the existing gnutls driver. For the packages there will be an additional package called rsyslog-openssl, while self-building users can enable this by running the configure with –enable-openssl. Openssl support is currently still experimental, but will become the preferred TLS driver. Feedback about this is especially appreciated.
Some time in the future, we will also retire support for liblogging-stdlog, as we suspected it is never used in practice. The plan is to disable use of liblogging-stdlog by default during configure. So users (and distros!) can still opt-in to have it enabled if they desire. A couple of releases later, we want to completely remove the functionality, except if there has desire been shown in the meantime which justifies to keep liblogging-stdlog.
There were also a lot of bugfixes added to this release, so please make sure to read the changelog.
Today, we release rsyslog 8.35.0. Apart from the usual fixes and small encancements, this release features extensive rework to accomodate oversized messages.
In the past, message that were bigger than defined by maxmessagesize were not handled correctly, though in most cases this was not really noticable. This is now taken care of and there are now several modes that can be defined to deal with such a case.
Adiscon is proud to announce the 12.0 release of MonitorWare Agent.
MonitorWare Agent now supports latest Windows 2016 and Windows 10 Creators update build 1709.
New load balancing capabilities have been added. This permits to balance load between multiple target syslog servers.
The log normalization capabilities have been greatly enhanced via a completely new method. It provides greater speed, enhanced ease of use and support for more complex normalization capabilities.
File monitoring has been enhanced in various ways, most importantly by providing the ability to define message seperation via regular expressions.
Performance has been slightly optimized and some minor features have been added. Full details are available via the version history.
Detailed information can be found in the version history.
Version 12.0 is a free download. Customers with existing 11.x keys can contact our Sales department for upgrade prices. If you have a valid Upgrade Insurance ID, you can request a free new key by sending your Upgrade Insurance ID to email@example.com. Please note that the download enables the free 30-day trial version if used without a key – so you can right now go ahead and evaluate it.
Today, we release rsyslog 8.34.0. Most notably is the large refactoring of the imfile module as well as the new module mmkubernetes (contributed). Additionaly, a lot of improvements and fixes have been added to the current release, too many to list them all. So please take a look at the changelog for all the details.
UTC is the so-called “universal coordinated time”. UTC was formerly referred to as “GMT” (Greenwich Mean Time) and is the basis of the international time zone system. For example, New York, USA is 5 hours behind UTC. So if it is 12 noon in New York, the UTC time is 5pm.
The MonitorWare line of products often uses UTC. UTC has the fast advantage of providing one consistent time notation, even if devices are across multiple time zones. This is extremely valuable if a centrel location is to consolidate events from senders in multiple time zones.
Using UTC might not be appropriate if a whole system is contained within a single time zone. As such, most time parameters inside the MonitorWare line of products can be configured to work with local time instead of UTC.
A non-reliable IP transport protocol. It provides best effort delivery. Typically, in LAN environments UDP packets are never lost. However, in WAN scenarios or with heavily loaded LANs, UDP packets might be lost.
Syslog Facility is one information field associated with a syslog message. It is defined by the syslog protocol. It is meant to provide a very rough clue from what part of a system the message originated from. Tradidionally, under UNIX, there are facilities like KERN (the OS kernel itself), LPD (the line printer daemon) and so on. There are also the LOCAL_0 to LOCAL_7 facilities, which were traditionally reserved for administrator and application use.
However, with the wide adaption of the syslog protocol, the facility field contents has become a little less clear. Most syslog enabled devices nowadays allow configuring any value as the facility. So it is basically left to distinguise different classes of syslog messages.
The facility can be very helpful to define rules that split messages for example to different log files based on the facility level.
Facility values are defined in RFC 3164:
The Facilities and Severities of the messages are numerically coded
with decimal values. Some of the operating system daemons and
processes have been assigned Facility values. Processes and daemons
that have not been explicitly assigned a Facility may use any of the
“local use” facilities or they may use the “user-level” Facility.
Those Facilities that have been designated are shown in the following
table along with their numerical code values.
0 kernel messages
1 user-level messages
2 mail system
3 system daemons
4 security/authorization messages (note 1)
5 messages generated internally by syslogd
6 line printer subsystem
7 network news subsystem
8 UUCP subsystem
9 clock daemon (note 2)
10 security/authorization messages (note 1)
11 FTP daemon
12 NTP subsystem
13 log audit (note 1)
14 log alert (note 1)
15 clock daemon (note 2)
16 local use 0 (local0)
17 local use 1 (local1)
18 local use 2 (local2)
19 local use 3 (local3)
20 local use 4 (local4)
21 local use 5 (local5)
22 local use 6 (local6)
23 local use 7 (local7)
Table 1. syslog Message Facilities
Note 1 – Various operating systems have been found to utilize
Facilities 4, 10, 13 and 14 for security/authorization,
audit, and alert messages which seem to be similar.
Note 2 – Various operating systems have been found to utilize
both Facilities 9 and 15 for clock (cron/at) messages.