Send Systemd Logs to Loggly
You can configure systemd or journald to send logs to Loggly using your default syslog daemon, so there are no proprietary agents needed. This guide will configure your system to send the standard Systemd logs, and offer a foundation to monitor file and application logs.
This Systemd logging guide assumes you have sudo access, you’re on a Systemd supported linux distribution with rsyslog 5.8 or higher, it receives local systemd logs, and port 514 is open to outbound connections. If you have different requirements, please see the Advanced Options below.
- Configure Syslog Daemon
Run our automatic Configure-Syslog script below to setup rsyslog. Alternatively, you can Manually Configure Rsyslog or Syslog-ng.
curl -O https://www.loggly.com/install/configure-linux.sh sudo bash configure-linux.sh -a SUBDOMAIN -u USERNAME
- SUBDOMAIN: your account subdomain that you created when you signed up for Loggly
- USERNAME: your Loggly username, which is visible at the top right of the Loggly console
You will need to enter your system root password so it can update your rsyslog configuration. It will then prompt for your Loggly password.
Open the /etc/systemd/journald.conf file and uncomment the following to send logs to syslog.
Copy and paste the following command in terminal to restart systemd-journal
systemctl restart systemd-journald
Search Loggly over the past sometime to logs with appName as journal. It may take a few minutes to index them. If you don’t see them, check the troubleshooting section below.
Advanced Systemd Logging Options
- Centralizing Systemd Logs – Discusses pros/cons of different approaches to centralizing systemd logs
- Troubleshoot Problems Using Linux Logs – Find the root cause of login failures, memory problems, and more
Troubleshooting Linux Syslog
- Try manually configuring rsyslog if the script doesn’t work
- See our Rsyslog Troubleshooting Guide
- Search or post your own question in the community forum.