<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Capacity-Planning on №42</title>
    <link>https://blog.no42.org/tags/capacity-planning/</link>
    <description>Recent content in Capacity-Planning on №42</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.no42.org/tags/capacity-planning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Breaking OpenNMS metric collection with SNMP</title>
      <link>https://blog.no42.org/article/breaking-opennms-collection-snmp/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.no42.org/article/breaking-opennms-collection-snmp/</guid>
      <description>&lt;p&gt;The most common question I get about OpenNMS at scale is some version of this: I have a lot of network equipment, I want SNMP performance data from all of it, how big does the box need to be?&#xA;The honest answer used to be &amp;ldquo;it depends&amp;rdquo;, followed by a shrug about agent behavior.&lt;/p&gt;&#xA;&lt;p&gt;What I reached for in those situations was the instrumentation log reader.&#xA;It tells you two things about a running system: how long it takes to collect metrics from your agents, and how long it takes to persist them.&#xA;The node inventory matters just as much.&#xA;It tells you the node-to-interface ratio and how the metric collection is composed in your environment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
