Skip to main content

Restarting this blog

This was my personal blog that I abandoned ~10 years ago in favor of a corporate blog.  I am reviving it and continue where I left off.

This blog has focused a lot on technology and syslog-ng particular and that is something I don't want to change. I work a lot on home automation these days so I expect that to creep in.

It's difficult to explain a decade in a blog post but a few items follow that I consider noteworthy:

* syslog-ng became pretty successful as a commercial offering while still keeping the open source version in shape. In this 10 years the project produced 23 major syslog-ng releases with lots of new stuff open source first.

* Balabit a company has grown to 250+ employees EUR 20m+ revenue and was eventually sold to a US company called Quest/One Identity in 2018

* I left Balabit a year and a half later in 2019, the company behind syslog-ng, the one I was a founder of.

syslog-ng is still thriving and is gaining momentum. This is true for both the open source project and the commercial offering (at least that's what I hear from ex colleagues).

I am pretty fortunate that even though I sold my stake in Balabit I can keep my  hobby:  syslog-ng. And this is because of open source. In a way I am becoming an external contributor to a project I was once the corporate herald for. Neat, eh?

Now, enough rambling, it's pretty late. Blogging is on!

Comments

Post a Comment

Popular posts from this blog

syslog-ng fun with performance

I like christmas for a number of reasons: in addition to the traditional "meet and have fun with your family", eat lots of delicious food and so on, I like it because this is the season of the year when I have some time to do whatever I feel like. This year I felt like doing some syslog-ng performance analysis. After reading Ulrich Deppert's series about stuff "What every programmer should know about memory" on LWN, I thought I'm more than prepared to improve syslog-ng performance. Before going any further, I'd recommend this reading to any programmer, it's a bit long but every second reading it is worth it. As you need to measure performance in order to improve it, I wrote a tool called "loggen". This program generates messages messages at a user-specifyable rate. Apart from the git repository you can get this tool from the latest syslog-ng snapshots. Loggen supports TCP, UDP and UNIX domain sockets, so really almost everything can be me
17 comments
Read more

syslog-ng roadmap 2.1 & 2.2

We had a meeting on the syslog-ng roadmap today where we decided some important things, and I thought I'd use this channel to tell you about it. The Open Source Edition will see a 2.1 release incorporating all core changes currently in the Premium Edition and additionally the SQL destination driver. We are going to start development on the 2.2 PE features, but some of those will also be incorporated in the open source version: support for the latest work of IETF syslog protocols unique sequence numbering for messages support for parsing message contents Previously syslog-ng followed the odd/even version numbering to denote development/stable releases. I'm going to abandon this numbering now: the next syslog-ng OSE release is going to have a 2.1 version number and will basically come out with tested code changes only. The current feature set in PE were developed in a closed manner and I don't want to repeat this mistake. The features that were decided to be part of the Open
12 comments
Read more

syslog-ng 3.0 and SNMP traps

Last time I've written about how syslog-ng is able to change message contents. I thought it'd be useful to give you a more practical example, instead of a generic description. It is quite common to convert SNMP traps to syslog messages. The easiest implementation is to run snmptrapd and have it create a log message based on the trap. There's a small issue though: snmptrapd uses the UNIX syslog() API, and as such it is not able to propagate the originating host of the SNMP trap to the hostname portion of the syslog message. This means that all traps are logged as messages coming from the host running snmptrapd, and the hostname information is part of the message payload. Of course it'd be much easier to process syslog messages, if this were not the case. A solution would be to patch snmptrapd to send complete syslog frames, but that would require changing snmptrapd source. The alternative is to use the new parse and rewrite features of syslog-ng 3.0. First, you need to f
2 comments
Read more