<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Loki on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/loki/</link>
    <description>Recent content in Loki on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/loki/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes Logging Operators: Fluent Operator vs Loki Operator vs Vector Operator</title>
      <link>https://www.pistack.xyz/posts/2026-05-07-self-hosted-kubernetes-logging-operators-fluent-loki-vector-guide/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-07-self-hosted-kubernetes-logging-operators-fluent-loki-vector-guide/</guid>
      <description>&lt;p&gt;Managing logs in Kubernetes clusters is fundamentally different from traditional server environments. Pods are ephemeral, log volumes are ephemeral, and the sheer volume of container stdout/stderr output can overwhelm simple log collection approaches. Kubernetes-native logging operators solve this problem by managing the entire log pipeline as Kubernetes resources — automatically discovering new pods, applying parsing rules, and forwarding logs to centralized storage. This guide compares three leading open-source Kubernetes logging operators: &lt;strong&gt;Fluent Operator&lt;/strong&gt;, &lt;strong&gt;Loki Operator&lt;/strong&gt;, and &lt;strong&gt;Vector Operator&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted Log Retention &amp; Lifecycle Management: Elasticsearch ILM vs Loki Retention vs OpenSearch ISM</title>
      <link>https://www.pistack.xyz/posts/2026-05-06-self-hosted-log-retention-lifecycle-management-elasticsearch-ilm-loki-opensearch-ism/</link>
      <pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-06-self-hosted-log-retention-lifecycle-management-elasticsearch-ilm-loki-opensearch-ism/</guid>
      <description>&lt;p&gt;Managing log retention is one of the most critical operational challenges for any self-hosted observability stack. Without proper lifecycle management, log indices grow unbounded, storage costs explode, and query performance degrades. Index Lifecycle Management (ILM), retention policies, and Index State Management (ISM) are the mechanisms that automate the movement, sizing, and deletion of log data across its useful lifetime.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
