<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Observability on DevOps &amp; Rock&#39;N&#39;Roll</title>
    <link>https://artazar.pages.dev/tags/observability/</link>
    <description>Recent content in Observability on DevOps &amp; Rock&#39;N&#39;Roll</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 19 Aug 2026 15:55:02 +0700</lastBuildDate>
    <atom:link href="https://artazar.pages.dev/tags/observability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Node labels for Node Exporter alerts</title>
      <link>https://artazar.pages.dev/blog/05-node-exporter-labels/</link>
      <pubDate>Wed, 04 Mar 2026 00:08:30 +0000</pubDate>
      <guid>https://artazar.pages.dev/blog/05-node-exporter-labels/</guid>
      <description>&lt;p&gt;Running a multipurpose Kubernetes cluster where production, dev and infra workloads share the same infrastructure is pretty common. In such a setup, you often want your alerting rules to be smarter: fire a critical alert when a prod node is burning CPU, but keep it informational for a dev node. To do that, you need your Prometheus metrics to carry environment context. This post shows how to thread that label all the way from a Karpenter node pool down to the Prometheus alert.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
