Is it safe to update Netdata?
Tracking netdata/netdata
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'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
Every verdict on Bumplog traces back to a GitHub release. No invented details.