<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Monitoring</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Monitoring feed</description>
    <item>
      <title>Article: Local-First AI Inference: A Cloud Architecture Pattern for Cost-Effective Document Processing</title>
      <link>https://www.infoq.com/articles/local-first-ai-inference-cloud/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Monitoring</link>
      <description>&lt;img src="https://res.infoq.com/articles/local-first-ai-inference-cloud/en/headerimage/Local-First-AI-Inference-A-Cloud-Architecture-Pattern-for-Cost-Effective-Document-Processing-header-1778141518292.jpg"/&gt;&lt;p&gt;The Local-First AI Inference pattern routes 70–80% of documents to deterministic local extraction at zero API cost, reserving Azure OpenAI calls for edge cases and flagging low-confidence results for human review. Deployed on 4,700 engineering drawing PDFs, it cut API costs by 75% and processing time by 55%, while bounding errors through a human review tier.&lt;/p&gt; &lt;i&gt;By Obinna Iheanachor&lt;/i&gt;</description>
      <category>Model Inference</category>
      <category>Generative AI</category>
      <category>Azure</category>
      <category>Observability</category>
      <category>Microsoft Azure</category>
      <category>Cost Optimization</category>
      <category>Artificial Intelligence</category>
      <category>GPT-4</category>
      <category>Cloud</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Mon, 11 May 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/local-first-ai-inference-cloud/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Monitoring</guid>
      <dc:creator>Obinna Iheanachor</dc:creator>
      <dc:date>2026-05-11T11:00:00Z</dc:date>
      <dc:identifier>/articles/local-first-ai-inference-cloud/en</dc:identifier>
    </item>
    <item>
      <title>Grafana's Kubernetes Monitoring Helm Chart v4 Brings Multiple Fixes</title>
      <link>https://www.infoq.com/news/2026/05/kubernetes-monitoring-helm/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Monitoring</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/05/kubernetes-monitoring-helm/en/headerimage/generatedHeaderImage-1777406799196.jpg"/&gt;&lt;p&gt;Grafana Labs has released version 4 of its Kubernetes Monitoring Helm chart, describing it as the most significant update the chart has received since its introduction. The release, announced in April 2026 by Pete Wall and Beverly Buchanan, addresses a range of configuration problems that had accumulated as users scaled to larger and more complex deployments.&lt;/p&gt; &lt;i&gt;By Matt Saunders&lt;/i&gt;</description>
      <category>Kubernetes</category>
      <category>Monitoring</category>
      <category>helm</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Wed, 06 May 2026 07:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/05/kubernetes-monitoring-helm/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Monitoring</guid>
      <dc:creator>Matt Saunders</dc:creator>
      <dc:date>2026-05-06T07:00:00Z</dc:date>
      <dc:identifier>/news/2026/05/kubernetes-monitoring-helm/en</dc:identifier>
    </item>
    <item>
      <title>Article: Three Pillars of Platform Engineering: a Virtuous Cycle</title>
      <link>https://www.infoq.com/articles/platform-reliability-cycle/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Monitoring</link>
      <description>&lt;img src="https://res.infoq.com/articles/platform-reliability-cycle/en/headerimage/platform-reliability-cycle-header-1777467114542.jpg"/&gt;&lt;p&gt;Platform engineering succeeds when reliability and ergonomics reinforce each other rather than compete. This article explores three foundational pillars: automated reliability, developer ergonomics, and operator ergonomics. Together, they establish a virtuous cycle that strengthens system stability, reduces operational burden, and empowers teams to scale infrastructure with confidence.&lt;/p&gt; &lt;i&gt;By Pratik Agarwal&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Observability</category>
      <category>Platform Engineering</category>
      <category>Developer Experience</category>
      <category>Site Reliability Engineering</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Tue, 05 May 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/platform-reliability-cycle/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Monitoring</guid>
      <dc:creator>Pratik Agarwal</dc:creator>
      <dc:date>2026-05-05T09:00:00Z</dc:date>
      <dc:identifier>/articles/platform-reliability-cycle/en</dc:identifier>
    </item>
  </channel>
</rss>
