<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Journald on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/journald/</link>
    <description>Recent content in Journald on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/journald/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Centralized Journal Collection: Graylog vs Vector vs systemd-journal-remote</title>
      <link>https://www.pistack.xyz/posts/2026-05-06-self-hosted-centralized-journal-collection-graylog-vector-systemd-journal-remote/</link>
      <pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-06-self-hosted-centralized-journal-collection-graylog-vector-systemd-journal-remote/</guid>
      <description>&lt;p&gt;Every Linux system running systemd generates structured journal entries through journald. These entries contain system logs, application output, kernel messages, and audit records — all in a binary format that is efficient for local querying but impractical for centralized analysis. Collecting journal entries from multiple servers into a single location enables cross-host correlation, centralized alerting, and long-term retention.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
