<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Graphite on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/graphite/</link>
    <description>Recent content in Graphite on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 03 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/graphite/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Graphite-Compatible Metrics Backends: Graphite-Web vs Go-Carbon vs Carbonapi vs VictoriaMetrics</title>
      <link>https://www.pistack.xyz/posts/2026-06-03-self-hosted-graphite-metrics-backends-graphite-web-go-carbon-carbonapi-victoriametrics/</link>
      <pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-03-self-hosted-graphite-metrics-backends-graphite-web-go-carbon-carbonapi-victoriametrics/</guid>
      <description>&lt;h2 id=&#34;why-self-host-your-metrics-backend&#34;&gt;Why Self-Host Your Metrics Backend?&lt;/h2&gt;&#xA;&lt;p&gt;Running your own metrics collection and storage infrastructure gives you full control over data retention, query performance, and infrastructure costs. When you&amp;rsquo;re monitoring hundreds of servers, containers, and services, having a dedicated metrics backend that fits your specific workload is essential. Cloud-based monitoring services can become prohibitively expensive at scale, and they introduce latency and data sovereignty concerns that many organizations cannot accept.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
