<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>logging on toorun.dev</title><link>https://toorun.dev/tags/logging/</link><description>Recent content in logging on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 23 Jul 2026 23:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/logging/index.xml" rel="self" type="application/rss+xml"/><item><title>Syslog Essentials: Forward Logs &amp; Key Configurations (Practical Guide)</title><link>https://toorun.dev/posts/syslog-essentials-log-forwarding-configuration/</link><pubDate>Thu, 23 Jul 2026 23:00:00 +0000</pubDate><guid>https://toorun.dev/posts/syslog-essentials-log-forwarding-configuration/</guid><description>Syslog Essentials: Forward Logs &amp;amp; Key Configurations Syslog (rsyslog) is the backbone of Linux logging. Here&amp;rsquo;s what you actually need to know to forward logs and configure it properly.
1) Minimal Setup: Forward All Logs to a Remote Server Edit /etc/rsyslog.d/10-forward.conf:
# Forward all logs to remote syslog server *.* @@remote-host.example.com:514 Explanation:
*.* = all facilities and severities @@ = TCP (use @ for UDP) 514 = standard syslog port Restart rsyslog:</description></item></channel></rss>