Installer syslog-ng avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt

Commandes et alias

• dqtool
• loggen
• pdbtool
• persist-tool
• syslog-ng
• syslog-ng-ctl
• syslog-ng-debun
• syslog-ng-update-virtualenv
• update-patterndb

Historique du projet

The project is associated with Balazs Scheidler, named by the upstream repository as the original creator and main developer. An official syslog-ng community post quotes Scheidler saying he began coding the first version in September 1998, after which the project grew from a syslogd replacement into a broader log-processing pipeline.

The upstream README describes syslog-ng as supporting classic syslog formats, JSON and unstructured input, parsers, files, message queues, SQL and NoSQL databases, and big-data destinations. It also notes Balabit as the original commercial sponsor and One Identity as the owner after Balabit's 2018 acquisition.

Historique d'adoption

The syslog-ng README says it is integrated into almost all Linux distributions and BSDs. The official community post says early adoption included Debian, Gentoo, SUSE, commercial Unix systems, default logging-daemon roles in some distributions, and embedding in commercial products.

The supplied package-manager facts list syslog-ng across Homebrew, Debian, Ubuntu, Fedora/dnf, Alpine/apk, Arch/pacman, MacPorts, and openSUSE/zypper, which matches its long-lived role as a portable logging component.

Modes d'utilisation

Package users typically install the daemon, edit syslog-ng.conf, then run syslog-ng or service-manager integration to collect local logs, accept network syslog, and forward or store the resulting event stream.

Its companion commands such as loggen, pdbtool, persist-tool, and syslog-ng-ctl matter to operators because packaging the project gives more than a daemon: it gives test generators, pattern-database tooling, control commands, and migration helpers.

Pourquoi les passionnés de paquets s'y intéressent

syslog-ng matters in package-manager culture because logging is infrastructure glue: distributions need a daemon with stable config paths, service integration, optional modules, and sane defaults.

It is also a classic example of a package whose value depends on compile-time feature detection and optional dependencies; packagers care about which destinations, parsers, TLS, database, and message-queue modules are enabled.

Chronologie

• 1998: Balazs Scheidler began coding the first version of syslog-ng.
• 2018: One Identity acquired Balabit, the original commercial sponsor named by the upstream README.
• 2026: The upstream README describes syslog-ng as integrated into almost all Linux distributions and BSDs.

Related projects

• syslog-ng sits in the syslog/log-processing family alongside traditional syslogd-style daemons and modern telemetry pipelines; the upstream README explicitly points to destinations such as Elasticsearch, Kafka, Hadoop, PostgreSQL, and MongoDB.

Sources

• https://github.com/syslog-ng/syslog-ng
• https://www.syslog-ng.com/community/b/blog/posts/the-syslog-ng-insider-2022-01-reboot-sequence-monterey-centos-9
• source_facts.package-manager