rsyslog

The rocket-fast system for log processing pipelines

Search Results for: feed

rsyslog 8.1.5 (v8-devel) released

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

We have just released 8.1.5 of the v8-devel branch. This release offers some important bug fixes and an enhanced imfile. It now supports inotify and has no longer a fixed limit on the number of files that can be monitored. Note that inotify must be enabled. By default, the previous polling mode is used. For details see parameter “mode” in the doc: http://www.rsyslog.com/doc/imfile.html
ChangeLog: http://www.rsyslog.com/changelog-for-8-1-5-v8-devel/
Download: http://www.rsyslog.com/rsyslog-8-1-5-v8-devel/

Feedback is *very much* appreciated.

Best regards, Florian Riedl

rsyslog 7.4.9 (v7-stable) released

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

We have just released 7.4.9 of the v7-stable branch.

While we initially did not intend to do another v7.4 release, we got some important fixes which we wanted to be available for 7.4, so we decided to do one more release. Note that also a new feature is included. The “processInternalMessages” global parameter now permits to tell rsyslog to send it’s own error messages to another system logger. This is most beneficial for systemd-based systems, where this permits rsyslog messages to show up in the service status command (but note that this requires configuration).

More detailed information is available in the ChangeLog.

ChangeLog:

http://www.rsyslog.com/changelog-for-7-4-9-v7-stable/

Download:

http://www.rsyslog.com/rsyslog-7-4-9-v7-stable/

As always, feedback is appreciated.

Best regards,
Florian Riedl

rsyslog 8.1.4 (v8-devel) released

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

We have just released 8.1.4 of the v8-devel branch.

This release adds the capability to set a variable based on a template. It also adds KEEPALIVE support to the RELP modules (which now require librelp 1.2.2+ for this reason). It also adds some usability enhancements and bug fixes.

Note that this release can be considered a “normal” devel version, with moderate risk associated to it. Experience in the past weeks suggest so. Special thanks to Pavel Levshin for all his work and tests. Still note that there is a considerably higher risk running the devel version than the stable one.

ChangeLog:

http://www.rsyslog.com/changelog-for-8-1-4-v8-devel/

Download:

http://www.rsyslog.com/rsyslog-8-1-4-v8-devel/

Feedback is *very much* appreciated.

Best regards,
Florian Riedl

rsyslog 7.5.8 (v7-devel) released

By Adiscon SupportPosted on Posted in News, Release AnnouncementTagged , , , , , ,
This is a candidate for the 7.6.0 release. As such, it is probably the last v7-devel release. It contains a select few enhancements, with very limited bug potential as well as some bug fixes.

Users are suggested to try out this versions and report errors. If we don’t learn of serious problems, we will most probably release 7.6.0 next week based on this code here.

More detailed information is available in the changelog.

ChangeLog:

http://www.rsyslog.com/changelog-for-7-5-8-v7-devel/

Download:

http://www.rsyslog.com/rsyslog-7-5-8-v7-devel/

As always, feedback is appreciated.

Best regards,
Florian Riedl

Support

Need Help?

Not far away, with options for everyone:

  • rsyslog mailing list
    An excellent place to talk the community, ask questions and provide feedback.
  • Frequently Asked Questions (FAQ)
    Maybe we have already solved your problem. Be sure to visit the FAQ area of the rsyslog web site!
  • Specific use-case
    If you want to have a specific setup, please make sure to visit the Guide area for rsyslog or Guide area for Rsyslog Windows Agent to see if a appropriate guide is available!
  • Enterprise Support is available for a fee
    This is for business users who require fast responses and someone who can be held accountable for supporting rsyslog (e.g. for compliance needs). Support is provided by Adiscon, the prime sponsor of rsyslog development.

See rsyslog documentation for potentially different support options.

There are additional support options for RSyslog Windows Agent only – please contact us via the Customer Service System for further information.

rsyslog 8.1.3 (v8-devel) released

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

We have just released 8.1.3 of the v8-devel branch.

This release contains further performance improvements. Note that both the output module interface and strgen interface have been changed and (some) modules may need to be modified. For the v8 supported rsyslog provided modules this has already be done (see v8 compatibility document for a list of supported modules). This release also detects failed actions more precisely. Finally, there are a couple of bug fixes in this release.

Note that this release can be considered a “normal” devel version, with moderate risk associated to it. Experience in the past weeks suggest so. Special thanks to Pavel Levshin for all his work and tests. Still note that there is a considerably higher risk running the devel version than the stable one.

ChangeLog:

http://www.rsyslog.com/changelog-for-8-1-3-v8-devel/

Download:

http://www.rsyslog.com/rsyslog-8-1-3-v8-devel/

Feedback is *very much* appreciated.

Best regards,
Florian Riedl

Changelog for 8.1.3 (v8-devel)

By Adiscon SupportPosted on Posted in ChangelogTagged , , , , , , ,

Version 8.1.3 [devel] 2013-12-06

THIS VERSION CAN BE CONSIDERED A “NORMAL” DEVEL RELEASE. It’s no longer
highly experimental. This assertion is based on real-world feedback.

  • changes to the strgen module interface
  • new output module interface for transactional modules
  • performance improvements
    • reduced number of malloc/frees due to further changes to the output module interface
    • reduced number of malloc/frees during string template processing
      We now re-use once allocated string template memory for as long as the worker thread exists. This saves us from doing new memory allocs (and their free counterpart) when the next message is processed. The drawback is that the cache always is the size of the so-far largest message processed. This is not considered a problem, as in any case a single messages’ memory footprint should be far lower than that of a whole set of messages (especially on busy servers).
    • used variable qualifiers (const, __restrict__) to hopefully help the compiler generate somewhat faster code
  • failed action detection more precisely for a number of actions
    If an action  uses string parameter passing but is non-transactional it can be executed immediately, giving a quicker indicatio of action failure.
  • bugfix: limiting queue disk space did not work properly
    • queue.maxdiskspace actually initializes queue.maxfilesize
    • total size of queue files was not checked against queue.maxdiskspace for disk assisted queues.

    Thanks to Karol Jurak for the patch.

Scroll to top