Posts Tagged ‘release’
Dear syslog-ng users,
This is the 20th issue of the syslog-ng Insider, a monthly newsletter that brings you syslog-ng related news.
Your feedback and news tips about the next issue is welcome at documentation(at)balabit.com
Video: a short introduction to syslog-ng
There is a video series in the work to introduce the basics of syslog-ng. The first video is online now, you can watch it.
New videos will be published on the same Youtube channel. You are very welcome to subscribe to receive notifications about further syslog-ng videos and other interesting content.
syslog-ng OSE configurator
syslog-ng OSE configurator is a web application, which can generate a syslog-ng OSE configuration with only a few mouse clicks. Right now it can only deal with global options, sources, destinations and of course with logpath. There are plans to add filters and templates in the future.
For more information and links to sources and the configurator, check the authors blog
syslog-ng 3.4 RC2 is released
Version 3.4 RC2 was released today. Compared to the RC1 release, it has some minor bugfixes, mainly related to fixing compile problems of different features and platforms. This also involves an update to the bundled ivykis library from version 0.30 to 0.36.
For a summary about what’s new in the 3.4 releases, check Bazsi’s blog at http://bazsi.blogs.balabit.com/2012/12/syslog-ng-3-4beta1-released/.
- For a list of changes, check the announcement
- For binary package availability check our 3rd party binary page
At the time of this writing there are RC1 packages for Debian, openSUSE, Ubuntu, FreeBSD ports are updated and there is a Fedora source rpm. These should be updated to RC2 in the coming days.
OpenSUSE Factory already features syslog-ng 3.4 RC1 and will be updated to RC2 after openSUSE 12.3beta1 is out.
- Right now 3.4 is available only in source form for Fedora. Check how you can compile it.
- FreeBSD 9.1 is released, news about the new release and syslog-ng are available
- Development of 3.5 is already started. A rough roadmap is available (GitHub account required)
Just before christmas I’ve released syslog-ng 3.4.0beta1, hopefully the last before the final release of syslog-ng 3.4. You can find the list of changes since 3.4.0alpha3 here.
Here’s the teaser for those wondering what 3.4 can do for them in addition to 3.3:
- Junctions, channels and the improved configuration format allows specifying log processing rules at even more flexibility.
- Full json support by the introduction of json-parser() and enhancements to $(format-json) template function.
- Support for the amqp() destination that implements support for the AMQP queueing protocol was added.
- MongoDB improvements to support replicasets, UNIX domain sockets. The performance was also improved by using insert operations instead of upserts.
- Added support for sending emails via the smtp() destination.
- Allow huge messages, instead of the old limits of 256k per message and 64k per value limits, the limits are 4GB for both.
- Added support for parsing the syslog message format after the initial reception. This can be used to “fix” messages before it actually reaches the syslog parser stuff.
- Native support for systemd.
- Demand loadable plugins to avoid having to explicitly write “@module” statements. This makes writing syslog-ng.conf files easier.
- A number of new template functions, like $(uuid), $(hash) and so on.
- A number of new macros $LOGHOST, $C_DATE and friends.
- A number of new parsers in db-parser, @PCRE@, @EMAIL@, @SET@, …
- Added rewrite operations to change message tags.
- Improved value-pairs expression support that allows specifying
More details can be found in the individual release announcements:
- 3.4.0alpha1: http://bazsi.blogs.balabit.com/2012/03/first-alpha-release-of-syslog-ng-3-4-published/
- 3.4.0alpha2: http://lists.balabit.hu/pipermail/syslog-ng/2012-May/018746.html
- 3.4.0alpha3: http://lists.balabit.hu/pipermail/syslog-ng-announce/2012-June/000144.html
As with all versions of syslog-ng, this wouldn’t have been possible without the help of the syslog-ng community. The role of the community is increasing with release-to-release, larger and larger features are contributed outside BalaBit and the number of contributors is increasing steadily too. I’d like to grab this opportunity to say thanks for everyone involved. Help is welcome and appreciated, be that code, documentation, a description of a use-case or simply just feedback. Thank you.
Stay tuned for the final version!
It seems that the BalaBit syslog-ng team that produces the Premium Edition of syslog-ng has beaten the community project this time, at least in terms of release date.
syslog-ng Premium Edition 4F1 (e.g. the first feature release past 4.0) has been released this week. It is the first release of PE in a long time that is actually based on an actual OSE core, namely 3.3.
I still have about 100 patches to review and integrate into OSE, hopedully with community involvement. But more about that in an upcoming post.
It is also interesting that some performanc testing was also done, and the new core does pretty well, and scales nicely on an 8 core machine, up to 800k msg/sec in @some onfigurations. Here’s the post the has some more details.
Now, if only the fixes they did were integrated properly to the OSE repository. but hey, life would be easy without challenges.
I just wanted to let you know, that fixes are nicely coming into the 3.3 beta tree, although it might not be very visible from th outside.
So if you consider trying out 3.3, I’d suggest to try a git snapshot instead of the 3.3beta1 tarball.
I’m trying to release a beta2 or rc1 in the near future. The version number depends on how much feedback we get until then
I’m glad to inform you all that the latest maintenance release for the long-term-supported SSB 2.0 line has been released. It contains lots of bugfixes, so you’re definitely advised to upgrade to it if you’re currently running SSB 2.0.0 or an engineering or update/security released based on that. For the detailed list of changes, see the full changelog, and head on to SSB’s download page to get the latest firmwares.
There are two things you should check before upgrading, though:
- The maximal acceptable size of a log message has been limited to 1000000 bytes on Log/Options.
- The maximum allowable memory for an indexer has been limited to 3GB on Log/Spaces.
In both cases, these were added as sanity checks to make sure you cannot accidentally set a limit which could cause unreliable operation. If your current limit is set above these values, make sure you change them before upgrading your SSB.
I’ve made a round of syslog-ng releases in the last couple of weeks.
From these 3.0.10 and 3.1.4 are quite similar, as they carry the almost the same set of bugfixes, which you can find in the respective changelogs. 3.2.2 is however different, it is a slightly larger update, as the 3.2.x branch of syslog-ng is the most recent. I’m quite happy how the 3.2.x beta period went, as the bugs found since the initial 3.2 release were not at all earthquakes: although they certainly affect some people, those are mainly in the newly introduced functionality (e.g. the correllation engine), the basic functionality of syslog-ng remained quite stable. And considering the size of the 3.1 -> 3.2 update, this is a result on its own.