rsyslog 8.36.0 (v8-stable) released

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.

ChangeLog:

https://github.com/rsyslog/rsyslog/blob/v8-stable/ChangeLog

Download:

http://www.rsyslog.com/downloads/download-v8-stable/

As always, feedback is appreciated.

Best regards,
Florian Riedl

rsyslog 8.35.0 (v8-stable) released

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.

ChangeLog:

https://github.com/rsyslog/rsyslog/blob/v8-stable/ChangeLog

Download:

http://www.rsyslog.com/downloads/download-v8-stable/

As always, feedback is appreciated.

Best regards,
Florian Riedl

RSyslog Windows Agent 5.0 Released

Adiscon is proud to announce the 5.0 release of Rsyslog Windows Agent.

Rsyslog Windows Agent fully 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 product now supports log normalization capabilities via a sophisticated high performance normalizer. This enables it to handle complex processing right at the message source.

Performance has been slightly optimized and some minor features have been added. Full details are available via the version history.

Version 5.0 is a free download. Customers with existing 4.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 sales@adiscon.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.

rsyslog 8.34.0 (v8-stable) released

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.

ChangeLog:

https://github.com/rsyslog/rsyslog/blob/v8-stable/ChangeLog

Download:

http://www.rsyslog.com/downloads/download-v8-stable/

As always, feedback is appreciated.

Best regards,
Florian Riedl

rsyslog 8.33.0 (v8-stable) released

Today, we release rsyslog 8.33.0. This release has a number of changes, but most of these are under the hood. Some of the more obivous changes are the new include() script object and template json container. Also, rsyslog now has better support for running in a container environment. The full list of changes to rsyslog can be reviewed in the Changelog.

ChangeLog:

https://github.com/rsyslog/rsyslog/blob/v8-stable/ChangeLog

Download:

http://www.rsyslog.com/downloads/download-v8-stable/

As always, feedback is appreciated.

Best regards,
Florian Riedl

New Logo Selected

The rsyslog community selected a new logo! The winner is logo 1, also shown here to the right. That logo won with an overwhelming majority, and lead the polls on the mailing list, our original logo selection post as well as a dedicated poll we created for easier and anonymous voting.

The logo was originally contributed in 2014 by “robert s”, whom unfortunately I am no longer able to contact. While before we never officially adopted it, it went into widespread use and is already often used to represent rsyslog. So in a sense the now-official selection let’s us keep consistent.

We are glad to have the community decision. I am right now implementing the new logo all over rsyslog web spaces. It will also be available via the rsyslog website github project (PR just created).

Many thanks to all who voted. It was a pleasant experience for us. This may have also set stage for future polls on different topics.

What are your thoughts regarding current and potential rsyslog support channels?

Overview

Traditionally the rsyslog community has sought and provided support through three main channels:

  • mailing list
  • forums
  • ticketing system (at one time Bugzilla, now GitHub)

Over the years, the community support options have shifted to the point that we are considering retiring the forums in order to best direct users that post there to other, more current options that better fit their needs. It would appear that aside from specific cases, the time of the web forum has passed.

That said, we would like to get your feedback to best determine the way to move forward. What follows are some initial ideas to get the conversation started. Please feel free to respond here, via Twitter, the mailing list or on GitHub. Thank you for your time.

Potential Support options

The following items are all “whiteboard” topics, listed in no real order in an effort to start discussion. Neither the order or presence in the list indicates that a decision has already been made by the team to pursue the support option. Please feel free to suggest your own entries.

Keep the forums, send notifications of new posts made on the forums to the mailing list

  • Note: Attempts to respond to those notifications would not result in the replies being posted to the original topic on the forums.
  • Would this truly result in any additional responses to those forum posts than are currently being provided now?

Set forums to read-only, direct visitors to GitHub for support

  • Could GitHub serve as a replacement for the forums? If so, what do you think about mixing general questions with bug reports in the main project (rsyslog/rsyslog)?
  • Would a dedicated “project” (e.g., rsyslog/rsyslog-support) be useful?

Set forums to read-only, direct visitors to StackOverflow

It would appear there is already solid participation there for questions tagged with rsyslog:

https://stackoverflow.com/questions/tagged/rsyslog

Official Twitter presence

followers are encouraged to retweet rsyslog related questions, guides, etc to their followers.

This is actually a “trick” entry of sorts! We already have a Twitter account that you can follow and interact with: @rsyslog

  • Do you already follow that account?
  • Would you retweet content from others?
  • Would you respond to help requests that are retweeted
  • If links to active GitHub issues are posted, will you take the time to go view them?

Official Facebook presence

Would you participate in discussions and support requests made there?

IRC, XMPP, Slack, …

  • Would you participate?
  • Do you feel this could replace the forums?
  • Would this be more useful to you than the mailing list?

Help select a logo…

We need a new, a real logo. We have some candidates. Note that  logo 1 was originally contributed in 2014 by “robert s” (whom I no longer able to contact…). Unfortunately, we did never officially adopt it, primarily due to failure on my part. Nevertheless it got pretty popular on the Internet and is often associated with rsyslog.

Please let us know what you like by leaving either a comment here or posting to the mailing list. Alternatively, you can also cast your ballot via this online vote form.

We are of course open for any additional suggestions. We are also not upset if you let us know that we are not great logo designers – we know we are not 😉

In order to avoid past errors, I ask anyone to provide feedback within one week, so we will draw a “winner” by Feb, 8th 2018. To help facilitate the decision I will experimentally put logo 1 into some places tomorrow if there is no strong objection in doing so.

If  you want to have a look at our old old ugly logo have a look at e.g. https://hub.docker.com/u/rsyslog/)

My personal 2cts: I as rsyslog maintainer (@rgerhards) have to admit that I have a strong preference for either logo 1 or logo 2.  Pro-logo 1 speaks IMHO that it is already associated with rsyslog. Together with its stylish simplicity, this makes it an excellent choice. I also need to say that I am a bit skeptic in regard to logo 6, simply because it breaks “r” and “syslog”.

RSyslog Windows Agent 4.3c Released

Adiscon is proud to announce the 4.3c release of Rsyslog Windows Agent.

This release contains some a minor bugfix.

Detailed information can be found in the version history below.

Build-IDs: Service 4.3.0.178, Client 4.3.0.255

Version 4.3c is a free download. Customers with existing 3.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 sales@adiscon.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.

Bugfixes

  • Property Engine: Fixed a bug that caused the first dynamic property to be missing when using XML report format. This bug also affected the Syslog TCP File-Caching feature (%rawsyslogmsg% missing).