<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ilm on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ilm/</link>
    <description>Recent content in Ilm 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/ilm/index.xml" rel="self" type="application/rss+xml" />
    <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>
