<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Prometheus on Daniel &#39;f0o&#39; Preussker</title>
    <link>https://f0o.dev/tags/prometheus/</link>
    <description>Recent content in Prometheus on Daniel &#39;f0o&#39; Preussker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 31 Mar 2025 10:25:56 +0000</lastBuildDate><atom:link href="https://f0o.dev/tags/prometheus/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PromCache</title>
      <link>https://f0o.dev/projects/2025/03/promcache/</link>
      <pubDate>Mon, 31 Mar 2025 10:25:56 +0000</pubDate>
      
      <guid>https://f0o.dev/projects/2025/03/promcache/</guid>
      <description>&lt;p&gt;Prometheus is a beast of a monitoring system, but Grafana dashboards can easily bring it to its knees. If you have ever set up a company-wide wallboard that auto-refreshes every ten seconds, or if you have multiple SRE teams querying the exact same raw metrics, you have probably seen your Prometheus CPU usage spike into a terrifying sawtooth pattern.&lt;/p&gt;
&lt;p&gt;The obvious solution is to slap an HTTP cache in front of it. But if you try doing that with a generic proxy like Varnish or Nginx, you will quickly realize it is completely useless.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>prom_hosts</title>
      <link>https://f0o.dev/projects/2021/04/prom_hosts/</link>
      <pubDate>Wed, 28 Apr 2021 06:47:28 +0000</pubDate>
      
      <guid>https://f0o.dev/projects/2021/04/prom_hosts/</guid>
      <description>&lt;p&gt;Standard flat-file &lt;code&gt;/etc/hosts&lt;/code&gt; name resolution is ancient, but it is still incredibly common in local home labs, small environments, and custom Kubernetes ingress networks. It is simple, stateless, and gets the job done without the headache of provisioning a heavy authoritative BIND or Knot DNS infrastructure.&lt;/p&gt;
&lt;p&gt;Most modern networks run CoreDNS to manage internal name resolution, and CoreDNS has a built-in &lt;code&gt;hosts&lt;/code&gt; plugin to serve zones straight from flat &lt;code&gt;/etc/hosts&lt;/code&gt; files.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
