Version 4.8 of AxoSyslog is our first independent release since AxoSyslog became a real syslog-ng™ fork (syslog-ng is a trademark of One Identity). In addition to the new features and bug fixes for issues reported in the AxoSyslog and the syslog-ng projects, with this release we’ve also started to publish RPM packages. This post shows you how to install AxoSyslog on RPM-based Linux distributions, like RHEL, Fedora, or AlmaLinux.
Note that AxoSyslog is also available in cloud-ready container images and via an APT repository. For details, see the AxoSyslog documentation.
Download AxoSyslog RPM packages
At the time of this writing, you can find the AxoSyslog RPM packages in the Assets section of the AxoSyslog GitHub Release pages for:
- Red Hat Enterprise Linux (RHEL) 9 / AlmaLinux 9
- Red Hat Enterprise Linux (RHEL) 8 / AlmaLinux 8
- Fedora 39
- Fedora 40
We are working on providing an RPM repository for the upcoming releases.
(The packages for AlmaLinux probably work for Rocky Linux 9 as well, but we haven’t tested it.)
Which package to install?
AxoSyslog supports many features. Some of these, like specific sources and destinations require additional packages that you need only if you’re actually using the specific destination. Therefore, AxoSyslog has a number of modules that you can install as a separate package if you need the particular feature. For example, to use the gRPC-based destinations (like loki() or opentelemetry()), install the axosyslog-grpc-*
package. For HTTP-based destinations like elasticsearch-http() or sumologic-http(), you need the axosyslog-http-*
package.
Usually, you install the base package axosyslog-<version-number>.<distro>.x86_64.rpm
, and the packages of specific modules that you want to use. We also provide debuginfo packages for every module, but you only need these in certain troubleshooting scenarios.
Install AxoSyslog on RHEL and AlmaLinux 9
To install AxoSyslog on RedHat Enterprise Linux 9 or AlmaLinux 9, complete the following steps. The instructions for AlmaLinux probably work for Rocky Linux 9 as well, but we haven’t tested it.
- Run the following commands to enable the EPEL repositories for your distribution. This is needed to install some dependencies of AxoSyslog. (For RHEL 8 and compatible distributions, use these instructions.)
- RHEL 9:
subscription-manager repos --enable codeready-builder-for-rhel-9-$(arch)-rpms dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
- AlmaLinux 9:
dnf config-manager --set-enabled crb dnf install epel-release
- RHEL 9:
- Download and extract the release tarball for your distribution, for example, on Almalinux 9:
wget https://github.com/axoflow/axosyslog/releases/download/axosyslog-4.8.0/rpm-almalinux-9.tar.gz tar –xvzf rpm-almalinux-9.tar.gz cd rpm-almalinux-9/
- Install AxoSyslog:
yum install ./axosyslog-4.8.0.2*
Install other packages for the modules you want to use as needed. For example, to use the gRPC-based destinations (like loki() or opentelemetry()), install the
axosyslog-grpc-*
package. For HTTP-based destinations like elasticsearch-http() or sumologic-http(), you need theaxosyslog-http-*
package. - Enable
syslog-ng
.systemctl enable syslog-ng systemctl start syslog-ng
- (Optional) If you don’t want to run other log collectors on the host, you can delete the existing one (which is rsyslog by default):
yum remove rsyslog.x86_64
Install AxoSyslog on Fedora
-
Download the release tarball for your distribution, for example, on Fedora 40:
wget https://github.com/axoflow/axosyslog/releases/download/axosyslog-4.8.0/rpm-fedora-40.tar.gz tar –xvzf rpm-fedora-40.tar.gz cd rpm-fedora-40/
-
Install AxoSyslog:
yum install ./axosyslog-4.8.0.2*
Install other packages for the modules you want to use as needed. For example, to use the gRPC-based destinations (like loki() or opentelemetry()), install the
axosyslog-grpc-*
package. For HTTP-based destinations like elasticsearch-http() or sumologic-http(), you need theaxosyslog-http-*
package. -
Enable
syslog-ng
.systemctl enable syslog-ng systemctl start syslog-ng
-
(Optional) If you don’t want to run other log collectors on the host, you can delete the existing one (which is rsyslog by default):
yum remove rsyslog.x86_64
Using AxoSyslog
After you’ve installed AxoSyslog, you can configure it just like syslog-ng
, using the same configurations files (/etc/syslog-ng/syslog-ng.conf
by default). For details, see the AxoSyslog documentation.
Getting help
If you run into any issues while installing or configuring AxoSyslog, or you have any questions, you can find us on our Discord server.
Summary
Thank you for everyone contributing with bug reports, feature requests, or pull requests. Feedback and any kind of contribution is always appreciated. Visit the AxoSyslog GitHub page or join Axoflow’s Discord server to reach out to us, or subscribe to the Axoflow newsletter to receive updates about AxoSyslog and our observability and logging-related products.
For an overview on how our platform enhances syslog-ng based log collection with metrics, see the Metrics for syslog-ng based log management infrastructures blog post.
Legal notice
syslog-ng is a trademark of One Identity LLC
Live Webinar
Parsing
sucks!
What can you do
about it?
30 October
10.00 PDT • 13.00 EDT • 19.00 CET
Balázs SCHEIDLER
Founder syslog-ng™
Mark BONSACK
Co-creator SC4S
Sándor GUBA
Founder Logging Operator
Neil BOYD
Moderator
Live Webinar
Parsing
sucks!
What can you do about it?
30 October
10.00 PDT • 13.00 EDT • 19.00 CET
Follow Our Progress!
We are excited to be realizing our vision above with a full Axoflow product suite.