rsyslog

The rocket-fast system for log processing

News

RSyslog Windows Agent 5.0 Released

By friedlPosted on Posted in Release AnnouncementTagged , , , , ,

Release Date: 2018-04-11

Build-IDs: Service 5.0.0.185, Client 5.0.0.263

Features

  • File Monitor: Added new options “Process rest of file as one message” and Read  Filebuffer size for better regex message separator handling.
  • Syslog Action: Added support for multiple syslog servers (Load balancing)
  • Syslog Action: Backup Syslog Server is now tried on connect as well. Before, the backup server was only used when an existing connection to the primary server interrupted.
  • Core Engine: Enhanced debug output for network errors.
  • LogNorm Action: Updated Action to support liblognorm v2 rulebases.

Bugfixes

  • Property Engine: Fixed daylight handling when using RFC3339 string conversion. Daylight was incorrectly always applied.
  • Property Engine: Fixed dynamic properties conversion when using xml output. This bug caused some properties to be missing when sending them by SETP protocol or using Syslog Cache mode.
  • Configuration reload: Fixed missing SNMP Mibtree after configuration reload.

You can download Free Trial Version of RSyslog Windows Agent.

rsyslog 8.34.0 (v8-stable) released

By friedlPosted on Posted in News, Release Announcement, UncategorizedTagged , , , , ,

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:

rsyslog 8.33.0 (v8-stable) released

By friedlPosted on Posted in News, Release AnnouncementTagged , , , ,

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:

New Logo Selected

By Rainer GerhardsPosted on Posted in Top News

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?

By deorenPosted on Posted in News, Top NewsTagged , , , , , ,

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?

    RSyslog Windows Agent 4.3c Released

    By Adiscon SupportPosted on Posted in Release AnnouncementTagged , ,

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

    RSyslog Windows Agent 4.3b Released

    By Adiscon SupportPosted on Posted in Release AnnouncementTagged ,

    Adiscon is proud to announce the 4.3b 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.177, Client 4.3.0.255

    Features

    Bugfixes

    • Property Engine: Fixed a bug related to the compressspace property replacer option that surfaced after recent stability changes. The bug stopped the option from working properly.

    Version 4.3b 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.

    rsyslog 8.32.0 (v8-stable) released

    By Adiscon SupportPosted on Posted in News, Release AnnouncementTagged , , , , ,

    Today, we release rsyslog 8.32.0. This realease, again, sports a vast number of changes. E.g. there are a number of new or updated build requirements, namely: libfastjson 0.99.8, libczmq >= 3.0.2 and libcurl. Otherwise most notably is the major update that ompgsql has received through contribution. Other changes include modules like pmrfc3164, omhiredis, mmexternal, omprog, imfile, omfile, mmpstrucdata. The full list of changes to rsyslog can be reviewed in the Changelog.

    We have also made some major changes to the RHEL/CentOS packages for rsyslog. We are now using a modified spec file from the CentOS base repository for building the EL7 release RPM. We decided to go this way out of several reasons. The major reason was a huge issue with the startup scripts that we used, which did not really work well on EL7 systems. More details are available here: http://www.rsyslog.com/major-centos7-rpm-changes/ and here: https://github.com/rsyslog/rsyslog/issues/2134#issuecomment-355483536

    Another reason is, that we wanted to make our own RPMs more similar to those in the base repository to avoid major conflicts in the future. That also means, that some additional module packages are not available anymore, because they are now included in the base rsyslog package (mmanon, mmutf8fix, ommail and pmaixforwardedfrom). All other additional sub-packages are still available.

    Because the Launchpad build environment [1] is currently unavailable, we cannot produce packages for Ubuntu at the moment. They will be published once the systems are available again.

    ChangeLog:

    [1] https://lists.ubuntu.com/archives/launchpad-announce/2018-January/000103.html

    Scroll to top