rsyslog

The rocket-fast system for log processing

Clarifying “AI First” – What It Really Means for rsyslog

By Rainer GerhardsPosted on Posted in AI/ML

TL;DR:
The rsyslog project is embracing AI First (Human-Controlled) — AI is becoming an integral partner across development, documentation, user education, technical support, deployment guidance, and future observability tools. This does not mean “vibe coding” or letting AI run unsupervised. Instead, AI accelerates routine work, drafts ideas, and provides insights, while Rainer Gerhards — with decades of battle-tested experience in IT, system logging, and software engineering — and the team remain in full control of strategy, design, and quality.
AI is improving rapidly, and we foresee delegating larger tasks (even parts of code design) to AI over time — but always with humans setting direction and standards.

“AI First” reflects our strategy of embedding AI across the project, from code and docs to observability, always under human guidance and quality control.
Continue reading “Clarifying “AI First” – What It Really Means for rsyslog”

Rsyslog Documentation Enters a New Era with AI-First Strategy

By Rainer GerhardsPosted on Posted in AI/ML, rsyslog documentation

TL;DR: We are rolling out a major documentation overhaul for rsyslog, powered by an AI-first strategy. This is the next step after our 2024 announcement on documentation and AI. At that time, AI tools were not yet ready for large-scale improvements, but with recent advances, we’ve accelerated our work. The result: a much more accessible, modern, and maintainable documentation set.

With current state of technology, AI can not auto-generate complete documentations. It needs to form a team with a human instead. (Image: Rainer Gerhards via AI)
Continue reading “Rsyslog Documentation Enters a New Era with AI-First Strategy”

rsyslog Goes AI First — A New Chapter Begins

By Rainer GerhardsPosted on Posted in AI/ML, News, Top News

After 24 months of focused evaluation and careful experimentation, we’re excited to announce a major shift in the evolution of rsyslog: we’re going AI First.

This marks the beginning of a strategic transformation in how we design, develop, and support rsyslog and its ecosystem. While today’s post is just a short announcement, it lays the groundwork for a series of updates to follow — including deep dives into what we’re doing, why, and how it benefits you.

rsyslog follows an AI First strategy.
Continue reading “rsyslog Goes AI First — A New Chapter Begins”

Revitalizing Rsyslog with Docker: A New Era of Log Management

By Rainer GerhardsPosted on Posted in News, Top NewsTagged

We’re excited to announce a renewed focus on the rsyslog Docker project, bringing you robust, flexible, and easy-to-use containerized solutions for your logging needs. This isn’t just a refresh; it’s a reimagining of how rsyslog can integrate into modern, containerized environments.

Continue reading “Revitalizing Rsyslog with Docker: A New Era of Log Management”

RSyslog Windows Agent 8.0 Released

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

Release Date: 2025-01-23

Build-IDs: Service 8.0.0.230, Client 8.0.0.320

Enhancements

  • DTLS Action: Added support for DTLS Action to enhance secure logging capabilities over the UDP protocol.
  • Property Engine: Added microseconds support to timestamps for improved precision (When parsing RFC 5424 timestamps).
  • OpenSSL: Updated OpenSSL library to a newer version and added TLS v1.3 compatibility testing.
  • RELP Action: Introduced custom output encoding options for improved flexibility.

Bugfixes

  • Syslog Action: Fixed memory leak in RFX5424 Syslog Header processing.
  • File Action: Improved handling for “LogRotation by time of the day” to prevent duplicate log rotations on the same day after restart.
  • Engine: Fixed invalid parameter issue during char-to-wchar_t conversion.

You can download Free Trial Version of RSyslog Windows Agent.

What to do when an External Script does not work?

By Rainer GerhardsPosted on Posted in News, rsyslog documentation

When a script runs fine interactively but fails in the rsyslog context (i.e., when executed by a background process or as part of a service) it typically indicates differences between the interactive environment and the service environment. Most importantly, it is not rsyslog itself you need to look at. Check the system config and debug your script so that you can obtain maximum information on why and when it fails.

Checking for issues with external scripts or plugins. (Symbol picture: Rainer Gerhards via AI)

If you know exactly that rsyslog cannot start the script, check that it has sufficient permissions and that all pathes are correct (use absolute pathes!).

Besides that general advice, here are some common reasons why the problem can happen and suggestions for debugging:

Continue reading “What to do when an External Script does not work?”
Scroll to top