<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Epok Blog</title>
    <link>https://epok.cloud/blog</link>
    <description>Detection-first observability — engineering notes on anomaly detection, root cause analysis, and alert discipline.</description>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://epok.cloud/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Detection-First Observability: Stop Searching, Start Being Told</title>
      <link>https://epok.cloud/blog/detection-first-observability</link>
      <guid isPermaLink="true">https://epok.cloud/blog/detection-first-observability</guid>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <description>Detection-first observability flips the model: instead of storing everything and handing you a search bar, the tool finds the problem and proves it. Here&apos;s why search-first is backwards.</description>
      <category>observability</category>
      <category>devops</category>
      <category>sre</category>
      <category>monitoring</category>
    </item>
    <item>
      <title>Root Cause Analysis Across Every Signal, On One Screen</title>
      <link>https://epok.cloud/blog/multi-signal-root-cause</link>
      <guid isPermaLink="true">https://epok.cloud/blog/multi-signal-root-cause</guid>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <description>Automated root cause analysis that reads logs, metrics, traces, infrastructure, and RUM together and cites every claim to its source, so you cut MTTR instead of hopping tabs.</description>
      <category>observability</category>
      <category>root-cause-analysis</category>
      <category>sre</category>
      <category>mttr</category>
      <category>incident-response</category>
    </item>
    <item>
      <title>How We Measure Detection Accuracy (and Admit When We&apos;re Not Sure)</title>
      <link>https://epok.cloud/blog/how-we-measure-detection-accuracy</link>
      <guid isPermaLink="true">https://epok.cloud/blog/how-we-measure-detection-accuracy</guid>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <description>Alert fatigue is a precision problem. How to weigh precision vs recall in monitoring — and why Epok caps its confidence and stays quiet on thin evidence.</description>
      <category>alert fatigue</category>
      <category>false positives</category>
      <category>detection</category>
      <category>accuracy</category>
      <category>monitoring</category>
      <category>rca</category>
    </item>
    <item>
      <title>When Fifty Alerts Are One Incident</title>
      <link>https://epok.cloud/blog/alert-storm-incident-grouping</link>
      <guid isPermaLink="true">https://epok.cloud/blog/alert-storm-incident-grouping</guid>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <description>An alert storm is fifty pages for one incident. How dedup, trace-ID incident grouping, dynamic suppression, and severity rationing cut the noise.</description>
      <category>observability</category>
      <category>devops</category>
      <category>sre</category>
      <category>monitoring</category>
      <category>on-call</category>
    </item>
    <item>
      <title>Stop Building Monitoring by Hand</title>
      <link>https://epok.cloud/blog/stop-building-monitoring-by-hand</link>
      <guid isPermaLink="true">https://epok.cloud/blog/stop-building-monitoring-by-hand</guid>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <description>Static thresholds and hand-built dashboards both rot. Why you should stop writing alert rules and let detection learn each service&apos;s baseline instead.</description>
      <category>monitoring</category>
      <category>alerting</category>
      <category>anomaly-detection</category>
      <category>dashboards</category>
      <category>observability</category>
    </item>
    <item>
      <title>The Incidents That Hide Between Alerts</title>
      <link>https://epok.cloud/blog/the-incidents-that-hide-between-alerts</link>
      <guid isPermaLink="true">https://epok.cloud/blog/the-incidents-that-hide-between-alerts</guid>
      <pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate>
      <description>The worst outages don&apos;t trip a threshold. A guide to missed incidents: silent services, slow cascades, new errors, latency drift — and how to catch them.</description>
      <category>detection</category>
      <category>incidents</category>
      <category>production</category>
      <category>observability</category>
      <category>alerting</category>
    </item>
    <item>
      <title>Why Your AWS Logging Bill Is Out of Control</title>
      <link>https://epok.cloud/blog/why-your-aws-logging-bill-is-out-of-control</link>
      <guid isPermaLink="true">https://epok.cloud/blog/why-your-aws-logging-bill-is-out-of-control</guid>
      <pubDate>Fri, 20 Mar 2026 00:00:00 GMT</pubDate>
      <description>Your CloudWatch bill climbs every month and nobody can say why. The real driver isn&apos;t the per-GB rate — it&apos;s the metering, cardinality, and DIY time.</description>
      <category>cloudwatch</category>
      <category>aws</category>
      <category>pricing</category>
      <category>comparison</category>
    </item>
    <item>
      <title>Datadog Alternatives for Small Teams (2026)</title>
      <link>https://epok.cloud/blog/datadog-alternatives-for-small-teams</link>
      <guid isPermaLink="true">https://epok.cloud/blog/datadog-alternatives-for-small-teams</guid>
      <pubDate>Wed, 18 Mar 2026 00:00:00 GMT</pubDate>
      <description>Datadog alternatives for small teams in 2026: an honest look at Grafana, Axiom, Better Stack, and Epok — by billing model, not just per-GB rate.</description>
      <category>datadog</category>
      <category>comparison</category>
      <category>pricing</category>
    </item>
    <item>
      <title>Catch New Errors in Production Before Your Users Do</title>
      <link>https://epok.cloud/blog/catch-new-errors-before-users-report-them</link>
      <guid isPermaLink="true">https://epok.cloud/blog/catch-new-errors-before-users-report-them</guid>
      <pubDate>Sun, 15 Mar 2026 00:00:00 GMT</pubDate>
      <description>The errors that take you down are the ones you&apos;ve never seen before. Here&apos;s how automatic fingerprinting catches new errors in production on the first occurrence.</description>
      <category>errors</category>
      <category>detection</category>
      <category>production</category>
      <category>alerting</category>
    </item>
    <item>
      <title>Silent Failures: The Bug That Won&apos;t Page You</title>
      <link>https://epok.cloud/blog/silent-failures-the-bug-that-wont-page-you</link>
      <guid isPermaLink="true">https://epok.cloud/blog/silent-failures-the-bug-that-wont-page-you</guid>
      <pubDate>Thu, 12 Mar 2026 00:00:00 GMT</pubDate>
      <description>A silent failure is when a service stops logging and no alert fires. Here&apos;s how absence detection catches the bug that never throws an error.</description>
      <category>silent failure</category>
      <category>absence detection</category>
      <category>monitoring</category>
      <category>alerting</category>
      <category>production</category>
    </item>
    <item>
      <title>20 Kubernetes Failures You Should Be Alerting On</title>
      <link>https://epok.cloud/blog/kubernetes-failures-you-should-alert-on</link>
      <guid isPermaLink="true">https://epok.cloud/blog/kubernetes-failures-you-should-alert-on</guid>
      <pubDate>Sun, 08 Mar 2026 00:00:00 GMT</pubDate>
      <description>CrashLoopBackOff is the one everyone watches. Here are 20 Kubernetes failures — in logs and events — that actually deserve an alert.</description>
      <category>kubernetes</category>
      <category>k8s</category>
      <category>alerting</category>
      <category>devops</category>
    </item>
    <item>
      <title>Why We Built Epok</title>
      <link>https://epok.cloud/blog/why-we-built-epok</link>
      <guid isPermaLink="true">https://epok.cloud/blog/why-we-built-epok</guid>
      <pubDate>Sat, 28 Feb 2026 00:00:00 GMT</pubDate>
      <description>We built Epok because we kept shipping dashboards nobody watched and alerts that missed real outages. The honest origin story of a detection-first tool.</description>
      <category>epok</category>
      <category>company</category>
      <category>detection-first</category>
      <category>observability</category>
      <category>root-cause-analysis</category>
    </item>
  </channel>
</rss>
