<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bumplog — is it safe to update Netdata?</title>
    <link>https://bumplog.org/apps/netdata/</link>
    <description>Update-safety verdicts for Netdata (netdata/netdata), traceable to the GitHub release.</description>
    <language>en</language>
    <atom:link href="https://bumplog.org/apps/netdata/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Netdata v2.10.3 — Safe to update</title>
      <link>https://bumplog.org/apps/netdata/</link>
      <guid isPermaLink="false">bumplog:app:netdata:v2.10.3:safe</guid>
      <pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate>
      <description>Safe to update. The release notes describe only bug fixes with no breaking changes, required migrations, or manual upgrade steps called out. The behavioral changes (SNMP uptime source, job-name validation) are backward-compatible by design — the existing metric name is preserved and stricter collector rules remain intact. What changed: v2.10.3 is a targeted patch release fixing four distinct bugs. Most notably, a shared-memory pool leak in the eBPF plugin has been resolved — on busy hosts this leak would exhaust a 32,768-slot pool within roughly 15 hours and then spin a CPU core at 100%, so the fix will noticeably reduce CPU consumption for affected users. The SNMP collector&apos;s uptime source has been switched to avoid a ~497-day counter wrap, while preserving the existing metric name and a fallback path. Dynamic config job-name validation was loosened for service discovery, vnode, and secret-store names to allow dots (e.g., FQDNs), and a PowerStore hardware struct field causing response-decoding errors was removed. Source release: https://github.com/netdata/netdata/releases/tag/v2.10.3</description>
    </item>
  </channel>
</rss>
