rsyslog 8.38.0 (v8-stable) released

Today, we release rsyslog 8.38.0.

This release has a lot of smaller changes and fixes. Worthy to point out are the fixes to make rsyslog build on AIX again, at least for a limited set of default modules.

Other changes and improvements are for more common use cases with modules like im-/omkafka, im(p)tcp, imfile, omelasticsearch and many more.

For more information, please check out the Changelog below.

There were also updated dependencies. The new release requires librelp 1.2.18.

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

EventReporter 16.1 Released

Adiscon is proud to announce the 16.1 release of EventReporter.

While this is a minor release, it offers considerable security
improvements for syslog. Now, when TLS/SSL is configured, the user has
full control over TLS options like ciphers, hashes and protocols.
There are GUI settings for the most common options, but also the
ability to provide in-depth detail configuration of each and every
aspect via TLS library specific strings. The insecure protocol list
has been updated and the SSLv2 protocol is now disabled by
default.

The property replacer has also been enhanced: it now supports the new
“cef” option to convert properties into a valid McAffee CEF FORMAT
string.

Detailed information can be found in the version history.Version 16.1 is a free download. Customers with existing 15.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.

WinSyslog 15.1 Released

Adiscon is proud to announce the 15.1 release of WinSyslog.

While this is a minor release, it offers considerable security
improvements for syslog. Now, when TLS/SSL is configured, the user has
full control over TLS options like ciphers, hashes and protocols.
There are GUI settings for the most common options, but also the
ability to provide in-depth detail configuration of each and every
aspect via TLS library specific strings. The insecure protocol list
has been updated and the SSLv2 protocol is now disabled by
default.

The RELP protocol has been upgraded to the newest version and now also
supports TLS/SSL.

The LogNorm Action has been hardened and supports / processes  Array types now

The property replacer has also been enhanced: it now supports the new
“cef” option to convert properties into a valid McAffee CEF FORMAT
string.

For more detailed information see the version history.Version 15.1 is a free download. Customers with existing 14.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 Windows Agent 5.1 Released

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

While this is a minor release, it offers considerable security
improvements for syslog. Now, when TLS/SSL is configured, the user has
full control over TLS options like ciphers, hashes and protocols.
There are GUI settings for the most common options, but also the
ability to provide in-depth detail configuration of each and every
aspect via TLS library specific strings. The insecure protocol list
has been updated and the SSLv2 protocol is now disabled by
default.

The RELP protocol has been upgraded to the newest version and now also
supports TLS/SSL.

The LogNorm Action has been hardened and supports / processes  Array types now

The property replacer has also been enhanced: it now supports the new
“cef” option to convert properties into a valid McAffee CEF FORMAT
string.

Full details are available via the version history.
Version 5.1 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.

MonitorWare Agent 12.1 released

Adiscon is proud to announce the 12.1 release of MonitorWare Agent.

While this is a minor release, it offers considerable security
improvements for syslog. Now, when TLS/SSL is configured, the user has
full control over TLS options like ciphers, hashes and protocols.
There are GUI settings for the most common options, but also the
ability to provide in-depth detail configuration of each and every
aspect via TLS library specific strings. The insecure protocol list
has been updated and the SSLv2 protocol is now disabled by
default.

The RELP protocol has been upgraded to the newest version and now also
supports TLS/SSL.

The LogNorm Action has been hardened and supports / processes Array types now

The property replacer has also been enhanced: it now supports the new
“cef” option to convert properties into a valid McAffee CEF FORMAT
string.

Detailed information can be found in the version history.

Version 12.1 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 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.37.0 (v8-stable) released

Today, we release rsyslog 8.37.0.

This release has a lot of smaller changes and fixes. They mostly revolve around general improvements in terms of error output and handling. There were also several enhancements for modules like ommail, omfile, imjournal and imrelp.

Notably is the work that went into the refactoring of the testbench, with newly enhanced plumbing and re-writing of most of the existing tests for better overview and easier test development.

For more details, please check out the Changelog below.

There were also updated dependencies. The new release requires librelp 1.2.17 and the packages have the most current version of librdkafka statically linked.

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

Support Forum Set to Read-Only Mode

Support forums have been a great way to communicate with users, but they have come out of style. Over the years, we have seen a steady decline in usage, and for the past couple of month postings have almost exclusively been spam. So we follow the trend and have set the forums to read-only mode. For support please use these channels:

Adiscon Products and Services: please mail info@adiscon.com

rsyslog open source project: use the rsyslog mailing list

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”.