What netdata/netdata shipped
Written by FoxPlug from the repository's own releases; not affiliated with Netdata. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/netdata/netdata; Netdata did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- Cloud data queries and parallel weights chunks no longer run on the libuv pool, so weight queries across many nodes and bursts of Cloud queries can no longer occupy every pool thread. Pull request #24581
- Health now keeps an alert's latest transition when saves arrive out of order, fixing parents that showed no alerts in Netdata Cloud while still having them raised. Pull request #24501
- The context worker now merges collected instance metadata under the context lock, removing a race with collectors creating or updating charts. Pull request #24645
- Query grouping now clamps resampling time and caps initial time-group buffers, so a very large
time_resamplingor gtime value can no longer cause an out-of-memory exit. Pull request #24630 - A filesystem whose kept mount is excluded is now charted, and the
thp_filemapping is fixed. Pull request #24444 - SNMP collects ifAlias as the
if_aliaslabel on interface charts, so ports can be filtered and grouped by the administrator-assigned description. Pull request #24552 - New BSD metrics bring FreeBSD ACPI battery capacity and committed memory, which Linux already had. Pull request #24617
- Chart labels ending in a backslash, such as an SNMP interface alias like C:\share\, are no longer corrupted by the plugins.d splitter. Pull request #24594
- Ppc32, mips32 and armv5 builds are fixed by changing the status save temp-file suffix counter to a 32-bit atomic. Pull request #24563
- Collectors can implement the optional Testable capability so explicit DynCfg tests run a different operation from startup Check. Pull request #24615
Why it matters
Several fixes this week address problems that could take down visibility or the agent itself: an out-of-order health save that left parents showing no alerts in Netdata Cloud, a pool starvation path in Cloud queries and parallel weights, and a query grouping allocation that could exit with out of memory. SNMP users also get ifAlias as a chart label and corrections to stock profile OIDs across many profiles, which makes interface data easier to identify and filter. Platform coverage improved as well, with missing FreeBSD metrics added and 32-bit target builds restored.
Changelog entry
- Move Cloud data queries and parallel weights chunks off the libuv pool so they cannot freeze it. Pull request #24581
- Keep an alert's latest transition when health saves arrive out of order. Pull request #24501
- Merge collected instance metadata under the context lock to avoid a race with chart updates. Pull request #24645
- Clamp resampling time and cap initial time-group buffers to prevent out-of-memory exits. Pull request #24630
- Chart a filesystem whose kept mount is excluded; fix
thp_filemapping. Pull request #24444 - Collect ifAlias as the
if_aliaslabel on SNMP interface charts. Pull request #24552 - Add missing FreeBSD metrics: ACPI battery capacity and committed memory. Pull request #24617
- Keep chart labels ending in a backslash intact. Pull request #24594
- Fix ppc32, mips32 and armv5 builds by using a 32-bit atomic for the status save suffix counter. Pull request #24563
- Support optional collector operational tests through the Testable capability. Pull request #24615
- Show the interface alias in the SNMP interfaces Function. Pull request #24595
- Derive SNMP table row identity from SNMP indexes instead of polling INDEX columns. Pull request #24625
This week: Cloud queries and parallel weights moved off the libuv pool; out-of-order health saves no longer drop a parent's alerts; SNMP interface charts now carry ifAlias as a label; FreeBSD gained missing memory and battery metrics; ppc32, mips32 and armv5 builds fixed.
Changes for Netdata users this week: Cloud data queries and parallel weights chunks no longer run as libuv pool jobs, so a weights query over many nodes or a burst of Cloud queries can no longer occupy every pool thread. Health keeps an alert's latest transition when saves arrive out of order, fixing parents that showed no alerts in Netdata Cloud while still having them raised. SNMP collects ifAlias as the if_alias label on interface charts, so ports can be filtered and grouped by the description an administrator assigns instead of the raw interface name. Stock profile OIDs were also corrected against MIBs and device captures. FreeBSD gains missing ACPI battery capacity and committed memory metrics, diskspace now charts a filesystem whose kept mount is excluded, and ppc32, mips32 and armv5
Week of October 26, 2026
What shipped
- Fixed a dbengine use after free that produced the DEADLOCK DETECTED fatal error in
datafile_acquire, caused byscan_data_filesleaving a pointer to a freed datafile during startup. Pull request #24509 - Keyed the dbengine page cache on the metric's uuidmap id instead of the METRIC address, so a new metric can no longer read pages left behind by a deleted metric. Pull request #24467
- Added chart reference holding while walking instance charts, closing paths in health variable lookups, the v2 alerts walk and query code where obsolete-chart cleanup could free a chart still in use. Pull request #24466
- Network Flows and OpenTelemetry traces functions now require a paid Netdata Cloud space in addition to signed-in, same-space and sensitive-data access. Pull request #24383
- Added acquired-label accessors for context instances so API and query code reads instance labels while holding the chart, instead of through an unheld chart pointer. Pull request #24474
- Applied small dbengine fixes from the F7 to F14 list, including removing a duplicate disk footprint check in the extent copy assertion. Pull request #24441
- ACLK https responses now strictly parse chunk sizes and cap chunked responses at 1 MiB, so a bad size line no longer makes the agent exit. Pull request #24483
- Added a shared 64 MiB ceiling on consumed HTTP response bodies, including after gzip expansion, returning an overflow error before further buffering. Pull request #24490
- Restored vnode stale timeouts and recovery by committing the timeout before cleanup and bringing scans forward for newly defined or reduced timeouts. Pull request #24495
- Fixed three Hyper-V charts in windows.plugin: VM CPU usage read 10x low, plus the GPA modification rate and storage latency charts. Pull request #24428
Why it matters
This week's changes close several crash and corruption paths in storage, including a use after free behind a long-standing dbengine fatal error and a page cache that could hand a new metric a deleted metric's pages. Access rules also changed for Network Flows and OpenTelemetry traces, which now need a paid Cloud space. Several fixes harden the agent against malformed remote or local input, such as oversized HTTP bodies and unchecked chunk sizes.
Changelog entry
- Dbengine: stop freeing a datafile that a journal index or cached page still references. Pull request #24509
- Dbengine: key the page cache on the metric's uuidmap id. Pull request #24467
- Contexts: hold a chart reference while walking instance charts. Pull request #24466
- Contexts: hold the chart while reading instance labels. Pull request #24474
- Dbengine: small fixes from the F7 to F14 list, one commit each. Pull request #24441
- Aclk: bound and strictly parse chunk sizes in https responses. Pull request #24483
- Go: bound shared HTTP response acquisition at 64 MiB. Pull request #24490
- Plugins.d: restore vnode stale timeouts and recovery. Pull request #24495
- Windows.plugin: fix Hyper-V VM CPU scale, GPA modifications rate and storage latency. Pull request #24428
- Network Flows and OpenTelemetry traces now require a paid Netdata Cloud space. Pull request #24383
- Threads: let owner-joined threads opt out of the shutdown drain. Pull request #24492
- Log2journal: stop JSON escapes from reading past the line terminator. Pull request #24365
This week: fixed the dbengine datafile use after free behind the DEADLOCK DETECTED fatal, keyed the page cache on metric ids, held chart references in context walks, capped chunked ACLK responses at 1 MiB, and put HTTP response bodies under a 64 MiB ceiling.
This week's work on Netdata: a use after free in dbengine that produced a long-standing fatal error at startup is fixed, and the page cache now keys on the metric id rather than a memory address. Context readers now hold a chart reference while reading instance labels and walking instance charts. On the network side, ACLK chunk sizes are strictly parsed and chunked responses capped at 1 MiB, and shared HTTP response bodies are bounded at 64 MiB. Network Flows and OpenTelemetry traces now require a paid Cloud space.
Week of October 19, 2026
What shipped
- Netdata v2.12.2 was released as a patch release addressing issues found since v2.12.1, tightening SNMPv3 authentication in the SNMP traps receiver and stopping alert evaluation from keeping obsolete charts alive indefinitely. Release
- The streaming sender no longer sends an HTTP Upgrade before streaming based on the parent using h2o option, which crashed the child on every connect since v2.8.0. Pull request #24426
- A host is now kept alive while remove-stale-node and the orphan or ephemeral host reaper remove it, closing use-after-free paths when a child reconnects during removal. Pull request #24353
- The
k8s_statecollector now marks obsolete only the charts of the deleted object itself instead of every chart whose ID starts with the deleted object's ID. Pull request #24402 - SQLite metadata database corruption that appears while the agent is running is now marked for recovery on the first failing step rather than only at clean shutdown. Pull request #24225
- Function call payloads now require strict JSON, preventing a crafted request body from injecting payload framing into external plugins and streaming children. Pull request #24409
- Function payload lines are treated as data until the exact payload end marker, so payload content that looks like a command can no longer replace or cancel calls. Pull request #24410
- The eBPF plugins now use compiled-in plugin, config and log directories when they gain privileges at exec, instead of environment variables from whoever starts them. Pull request #24412
- The Windows plugin adds more Exchange metrics for monitoring Exchange servers. Pull request #22117
- A Rust Tests workflow now runs cargo test for the src/crates workspace on pull requests and master pushes that touch Rust code. Pull request #24396
Why it matters
This week brings a patch release plus fixes that make the agent more robust in day-to-day operation: streaming reconnects no longer crash, stale-node removal no longer frees hosts still in use, and metadata database corruption is caught sooner. Kubernetes monitoring stops deleting unrelated charts, privileged eBPF plugins resolve their directories safely, and Windows gains more Exchange visibility.
Changelog entry
- Release v2.12.2 with SNMPv3 authentication tightening and obsolete chart lifetime fixes. Release
- Streaming: remove the h2o upgrade path from the sender that crashed children on connect. Pull request #24426
- Streaming: pin a host while remove-stale-node removes it to avoid use-after-free. Pull request #24353
- Go.d/k8s_state: remove only the deleted object's charts, not charts with matching ID prefixes. Pull request #24402
- SQLite: mark runtime metadata corruption on the first failing step and count queries once. Pull request #24225
- Functions: require strict JSON payloads between the payload markers. Pull request #24409
- Go.d: keep function payload lines out of command parsing. Pull request #24410
- EBPF: use compiled-in directories when the plugin runs with elevated privileges. Pull request #24412
- Windows plugin: add more Exchange metrics. Pull request #22117
- CI: run Rust workspace tests when Rust code changes. Pull request #24396
- Installer/updater: handle curl exit status 56 as a protocol failure. Pull request #24276
- Config: log the clamped value when update every exceeds the maximum. Pull request #24378
Netdata v2.12.2 is out. This week also fixes a streaming crash on connect, host removal races, Kubernetes charts for similarly named objects, and SQLite corruption detection. Plus more Exchange metrics on Windows and Rust tests in CI.
Netdata v2.12.2 is a patch release that tightens SNMPv3 authentication in the SNMP traps receiver, stops alert evaluation from keeping obsolete charts alive, and makes Cloud see disconnected children as offline. Alongside it, this week brings a streaming fix that ends a crash on every connect, host removal that no longer frees a host still in use, Kubernetes chart cleanup that only removes the deleted object's charts, earlier detection of SQLite metadata corruption, payload framing checks for function calls, and eBPF plugins that use compiled-in directories when privileged. Windows gains more Exchange metrics, and Rust code changes now get cargo test in CI.
Week of October 12, 2026
What shipped
- Go.d configurations that share a collector and job name can now act as alternative connection attempts, so a failed startup can advance to another eligible configuration while only one runtime collects for that job. Pull request #24350
- Otel-streams load generators now recover from websockets that go silent without closing, and jetstream no longer drops account events with valid statuses. Pull request #24357
- The parent now waits 125% of the child's reboot time, capped at 30 s, before reporting a child offline, correcting an integer calculation that made it wait only 100%. Pull request #24343
- A disconnected child is now reported to Cloud only after its online flag is cleared, so the offline state is no longer lost when the sync thread evaluates the update first. Pull request #24285
- Reconnect backoff clamp values are now returned in milliseconds, so retries at the cap wait as configured instead of about one second. Pull request #24340
- MQTT packet id allocation no longer returns id 1 twice when the 16-bit counter wraps, which could leave two in-flight QoS1 packets sharing an id. Pull request #24341
- A chart re-created with the same id now keeps the instance it took over, fixing a fatal RRDINSTANCE not linked to RRDSET error and its metric-level counterpart. Pull request #24349
- Alert evaluation no longer refreshes a chart's last-accessed time, so obsolete charts that still have alerts can be cleaned up and freed. Pull request #24273
- Static aarch64 agents on Cortex-A53 boards now work around errata 835769 and 843419, which caused SIGILL crashes a few seconds after start. Pull request #24207
- Agents add a _system_l4t_version host label, read from /etc/nv_tegra_release, so Jetson nodes can be filtered by their installed Jetson Linux release. Pull request #24323
Why it matters
This week fixed several defects that made parents hold child state longer than intended: children reported live to Cloud after disconnecting, obsolete charts kept alive by alert evaluation, and the offline wait capped by an integer bug. It also corrected connection and retry handling in go.d, otel-streams and the MQTT reconnect path, and made static aarch64 agents stop crash-looping on Cortex-A53 boards. Users get steadier long-running parents and agents that start and stay up.
Changelog entry
- Go.d: same-name collector jobs can act as alternative connection attempts. Pull request #24350
- Otel-streams: reconnects websockets that go silent and keeps jetstream account events with valid statuses. Pull request #24357
- Streaming: parent waits 125% of child reboot time before reporting the child offline. Pull request #24343
- Streaming: child is reported to Cloud only after it is actually offline. Pull request #24285
- Aclk: reconnect backoff clamps are returned in milliseconds. Pull request #24340
- Aclk: MQTT packet id 1 is no longer issued twice at counter wrap. Pull request #24341
- Contexts: a re-created chart keeps the instance and metrics it took over. Pull request #24349
- Health: alert evaluation no longer keeps obsolete charts alive. Pull request #24273
- Static aarch64 builds work around Cortex-A53 errata 835769 and 843419. Pull request #24207
- Daemon: exposes the Jetson Linux release as the _system_l4t_version host label. Pull request #24323
- Go.d: candidate recovery stays private across enable replies and waits. Pull request #24367
- Contexts: archived instance labels are not loaded for queries without a label filter. Pull request #24325
This week: go.d alternative configs for same-name jobs, otel-streams websocket reconnect, the 125% child offline wait now actually applied, offline reported only after the online flag clears, reconnect backoff clamps fixed, and static aarch64 agents on Cortex-A53 no longer crash-
This week's work on Netdata covered several reliability fixes across the agent and parent. go.d configurations sharing a collector and job name can now serve as alternative connection attempts, and otel-streams load generators recover from websockets that go silent. The parent again waits 125% of a child's reboot time before reporting it offline, and only reports after the online flag is cleared. Reconnect backoff clamps return milliseconds, and MQTT packet id 1 is no longer handed out twice at counter wrap. Re-created charts keep the instance they took over, and alert evaluation no longer keeps obsolete charts alive. Static aarch64 agents on Cortex-A53 boards work around two errata that caused SIGILL crash loops, and a new host label exposes the Jetson Linux release.
Week of October 5, 2026
What shipped
- Netdata v2.12.0 was released, with the Windows Agent build removed from the release page because of startup crashes traced to an upstream bug in a dependency. Release
- Netdata v2.12.1 shipped as a patch release that fixes a Windows Agent startup crash and a timezone detection bug, stabilizes the eBPF collector across more kernels and libbpf versions, and reduces Docker collector load. Release
- The experimental Go IPMI plugin now supports all Go Linux architectures instead of only amd64 and arm64, and stays Linux-only and disabled by default. Pull request #24215
- The experimental IPMI plugin can now collect from a remote BMC over LAN and LAN+, so one job can monitor a local OpenIPMI device or a remote BMC. Pull request #24216
- The Jetson collector now collects current power per rail, adding power rail charts alongside the existing GPU and EMC charts. Pull request #24204
- SNMP traps from SNMPv3 users configured with authentication now require authentication, so a noAuthNoPriv message naming such a user is no longer accepted. Pull request #24188
- SNMP connection info no longer includes the v1/v2c community or SNMPv3 passphrases in clear text, as the string is built from security level and USM user instead. Pull request #24217
- Host labels are loaded from the config file the Agent actually loaded, including one passed with -c FILE, and labels deleted from that file are removed on reload-labels. Pull request #24117
- The DEM GeoIP sources now support Agent-aware cache and stock discovery, explicit overrides and automatic refresh, and expose source availability through rum-sites. Pull request #24192
- Ndsudo no longer waits forever on root commands that cannot be signaled, so a hung command with no output returns after its timeout instead of blocking the call. Pull request #24189
Why it matters
This week brought two Agent releases, including a patch that addresses the Windows startup crash and timezone bug from the previous build, plus wider eBPF stability and lower Docker collector load. Alongside that, the experimental Go IPMI plugin gained architecture support and remote BMC collection, and SNMP handling stopped leaking secrets into debug logs. A number of collectors and background paths were tuned, from Jetson power rails to proc file lookups, host label reloading and DEM GeoIP handling.
Changelog entry
- Published Netdata v2.12.0, removing the Windows Agent installer from the release page due to startup crashes from an upstream bug. Release
- Released Netdata v2.12.1 with fixes for a Windows Agent startup crash and timezone detection bug, wider eBPF kernel stability, and lower Docker collector load. Release
- Extended the experimental Go IPMI plugin to all Go Linux architectures by dropping the amd64/arm64 restriction. Pull request #24215
- Enabled LAN and LAN+ remote BMC collection in the experimental IPMI plugin. Pull request #24216
- Added per-rail power consumption charts to the Jetson collector. Pull request #24204
- Required authentication for SNMPv3 traps from users configured with an authentication protocol. Pull request #24188
- Removed SNMP community strings and SNMPv3 passphrases from the logged connection info string. Pull request #24217
- Reloaded host labels from the Agent's active config file, including one passed with -c FILE, and removed labels deleted from that file. Pull request #24117
- Reworked DEM GeoIP loading to use Agent-aware discovery, explicit overrides and automatic refresh, and exposed source availability via rum-sites. Pull request #24192
- Kept RunNDSudo's timeout for root commands that cannot be signaled. Pull request #24189
- Made RUM installation explicit and receiver-hosted, using the configured
public_urland listener address. Pull request #24187 - Avoided unnecessary POLLOUT polling for streaming senders and receiver. Pull request #24203
Two releases this week: v2.12.1 fixes the Windows Agent startup crash and timezone bug, stabilizes eBPF across more kernels, and cuts Docker collector load. Also: Go IPMI now covers all Linux architectures and remote LAN BMCs, and SNMP no longer logs secrets.
This week Netdata shipped v2.12.1, a patch release that fixes a Windows Agent startup crash and a timezone detection bug, stabilizes the eBPF collector across a wider range of kernels and libbpf versions, and reduces the load the Docker collector places on the system. v2.12.0 was also published, with its Windows installer removed from the release page because of startup crashes traced to an upstream bug. On the collectors side, the experimental Go IPMI plugin now supports all Go Linux architectures and can collect from remote BMCs over LAN and LAN+, the Jetson collector added per-rail power, and SNMP stops putting communities and v3 passphrases in debug logs. Host labels now reload from the config file the Agent loaded, and DEM gained Agent-aware GeoIP refresh and explicit RUM installation
Week of September 28, 2026
What shipped
- Released v2.12.0 with OpenTelemetry Traces in Early Access, Redfish out-of-band server hardware monitoring, SNMP Topology diagnostics, new S3 and SMBIOS collectors, and reworked Ceph monitoring. Release
- Dem.plugin now runs Playwright journeys and Lighthouse desktop audits natively alongside browser RUM pageviews, with per-attempt history and investigation features. Pull request #24137
- Introduced dem.plugin using the Go framework with managed receiver and site jobs, RUM charts, Functions, SQLite history, OTLP export, and alerts. Pull request #24129
- Traces queries now read evicted files back from remote storage, and span searches report span count per service. Pull request #24088
- The redis collector now supports Redis-compatible servers including Valkey, Dragonfly, KeyDB, Kvrocks, and Garnet. Pull request #24130
- Prometheus collector adds
counter_raw_chartsoption to display a counter's raw value alongside its per-second rate. Pull request #24103 - Nd-run now offers opt-in Linux process-tree supervision with Go support for cancellation and verified cleanup of descendants. Pull request #24135
- Windows.plugin gains missing.NET CLR metrics and switches CLR collection from object-level totals to per-instance metrics. Pull request #22219
- Native scripts now declare metric and check metadata inside each collection snapshot, eliminating the need for separate metrics and checks sections in manifests. Pull request #24096
- Windows monitoring now includes support for Cluster Shared Volumes (CSV) in failover clustering environments. Pull request #23720
Why it matters
Version 2.12.0 brings significant monitoring expansions: native browser journey and audit collection through DEM, OpenTelemetry traces in early access, and out-of-band hardware monitoring with Redfish. Support for Redis-compatible servers and Windows clustering workloads extends platform coverage. The refactored native scripting system simplifies integration authoring by eliminating separate metadata files.
Changelog entry
- Released v2.12.0 with OpenTelemetry Traces Early Access, Redfish, SNMP Topology, S3, SMBIOS, Ceph rework, Windows Hyper-V/RDP/Cluster Shared Volumes Release
- Dem.plugin: add native Playwright journeys and Lighthouse desktop audits with per-attempt history and investigation features Pull request #24137
- Dem.plugin: introduce Go framework with managed jobs, RUM charts, Functions, SQLite history, OTLP export, alerts (experimental, disabled by default) Pull request #24129
- Go.d/redis: support Redis-compatible servers (Valkey, Dragonfly, KeyDB, Kvrocks, Garnet) Pull request #24130
- Go.d/prometheus: add
counter_raw_chartsto display counter raw values alongside per-second rates Pull request #24103 - Otel-traces: read evicted files from remote storage; search rows report span count per service Pull request #24088
- Nd-run: add opt-in Linux process-tree supervision with Go cancellation support Pull request #24135
- Windows.plugin: add missing.NET CLR metrics; switch from object-level totals to per-instance collection Pull request #22219
- Scripts.d: native scripts declare metadata inside collection snapshots, eliminating separate manifest sections Pull request #24096
- Windows.plugin: add Cluster Shared Volumes (CSV) monitoring Pull request #23720
- Plugins.d: restart external plugins after protocol errors instead of disabling permanently Pull request #24051
- Fix global SQLite stalls by replacing global lock with lifetime leases per connection Pull request #24099
Netdata v2.12.0: OpenTelemetry Traces, Playwright journeys and Lighthouse audits in dem.plugin, Redfish hardware monitoring, Redis-compatible servers, and Windows Cluster Shared Volumes support.
Netdata v2.12.0 ships with OpenTelemetry Traces in Early Access, enabling observability across tracing, metrics, and logs. dem.plugin now runs Playwright journeys and Lighthouse audits natively. Redfish brings out-of-band hardware monitoring. New support for Redis-compatible servers (Valkey, Dragonfly, KeyDB, Kvrocks, Garnet). Windows gains Hyper-V, RDP, and Cluster Shared Volumes monitoring. The native scripting system now eliminates separate metadata files.
Week of September 21, 2026
What shipped
- The Go StatsD collector now runs as a standalone statsd.d.plugin with its own entry point and configuration instead of as part of go.d. Pull request #24016
- Source archives are now available compressed with zstd, producing roughly 30% smaller files than gzip while decompressing faster. Pull request #22440
- StatsD listener configuration now supports a 'both' protocol option to bind UDP and TCP on the same address, and adds duration idle timeout configuration. Pull request #24028
- Database engine flush deadlock in the libuv worker pool is fixed by bounding flush workers and deferring excess work. Pull request #24027
- Host label changes now forward through streaming parents without reconnecting while keeping Cloud node info and alert matching current. Pull request #24015
- Idle NetIPC CPU use on 32-bit time64 Linux is fixed by updating the vendored NetIPC library to handle the futex syscall correctly. Pull request #24049
- Function responses from freeipmi.plugin are now serialized with chart output to prevent chart lines from being read as part of the response. Pull request #24052
- Function responses from apps.plugin are now serialized with chart output using proper mutex protection. Pull request #24050
- SMBIOS memory collector now identifies slots by both bank and device locator to handle boards that reuse device locators across channels. Pull request #24043
- Go.d collectors can now classify Init/Check failures as permanent or temporary errors with shared lifecycle error classification. Pull request #24004
Why it matters
This week focused on fixing synchronization issues between chart output and function responses that could corrupt protocol streams, improving StatsD as a standalone plugin, and addressing database and SNMP reliability across streaming and time handling. Several fixes target flaky tests and race conditions in the configuration and secret management systems.
Changelog entry
- StatsD collector now runs as standalone statsd.d.plugin Pull request #24016
- Zstd-compressed source archives available alongside gzip Pull request #22440
- StatsD: 'both' protocol option for UDP+TCP and duration idle timeout Pull request #24028
- Fix database engine flush deadlock in libuv worker pool Pull request #24027
- Host label forwarding through streaming parents without reconnect Pull request #24015
- Fix idle NetIPC CPU use on 32-bit time64 Linux Pull request #24049
- Serialize freeipmi.plugin function responses with chart output Pull request #24052
- Serialize apps.plugin function responses with chart output Pull request #24050
- SMBIOS memory: identify slots by bank and device locator Pull request #24043
- Go.d collectors: PermanentError and TemporaryError lifecycle classification Pull request #24004
- SNMP: handle sysObjectID as OctetString instead of ObjectIdentifier Pull request #24031
- NetFlow plugin: publish nothing until UDP listeners are bound Pull request #24029
- Fix SQLite status checks and ACLK protobuf serialization failures Pull request #24012
- Fix 64-bit timestamp formatting on 32-bit targets Pull request #23991
- Correct const qualifiers and pointer casts in C code Pull request #23998
New: StatsD runs as statsd.d.plugin. Fixes: function response serialization, database flush deadlock, idle CPU on 32-bit time64, SMBIOS slot identification, host label streaming. zstd archives now available.
This week's updates strengthen Netdata's reliability across multiple fronts. StatsD is now a standalone plugin with better configuration options. We fixed critical synchronization bugs where function responses could be corrupted by chart output, database flush deadlocks in the libuv pool, and idle CPU consumption on 32-bit time64 systems. SNMP and SMBIOS collectors are more robust, host labels stream properly through parents, and zstd-compressed archives reduce download sizes by 30%. Over 40 pull requests landed, mostly addressing race conditions, test flakiness, and protocol correctness.
Week of September 14, 2026
What shipped
- New
smbios_memorycollector for Linux reads SMBIOS firmware tables and reports physical memory inventory with persistent loss detection. Pull request #23965 - V2 collectors can now add, remove, and replace named native chart templates at runtime while preserving unchanged entries' lifecycle state. Pull request #23971
- Redfish collector chart template rebuilt from 10,223 lines of generated defaults to 4,000 lines of curated configuration. Pull request #23957
- Legacy shell-format alarm notification configuration now maps to 23 Go providers with ordered overlays and recipient policies. Pull request #23930
- Redfish collector enriched with optional hardware columns for processor counts, memory, storage details, firmware dates, and assembly revisions. Pull request #23950
- Redfish collector adds on-demand BMC logs viewer with event filtering by time, severity, and text. Pull request #23943
- V2 collector per-job collection status and duration charts restored, shared with V1 rendering. Pull request #23946
- Journal access diagnostics expanded to capture all three permission-granting mechanisms with optional plugin debug mode. Pull request #23947
- Discovered targets can now reference secrets when explicitly trusted by their collection pipeline. Pull request #23918
- Documentation added for secret-resolution execution privileges and SNMP scan credential exposure on Linux and Unix systems. Pull request #23923
Why it matters
This week adds hardware inventory collection via SMBIOS, significantly improves Redfish functionality with logs viewing and enriched hardware details, and maps legacy alarm notification systems to modern providers. Support and debugging capabilities also improve for journal access and secret handling.
Changelog entry
- Add
smbios_memorycollector for Linux memory inventory and persistent loss detection Pull request #23965 - Support named active chart template sets in V2 collectors with runtime add/remove/replace Pull request #23971
- Refactor Redfish chart template from 10,223 to 4,000 lines, removing generated defaults Pull request #23957
- Add optional Redfish hardware columns for processor, memory, storage, and firmware details Pull request #23950
- Add Redfish on-demand BMC logs viewer with time, severity, and text filtering Pull request #23943
- Map legacy alarm notification settings to 23 Go providers with config overlays Pull request #23930
- Restore V2 collector per-job status and duration charts Pull request #23946
- Expand journal access diagnostics to capture all three permission mechanisms Pull request #23947
- Allow per-pipeline trust of discovered targets for secret references Pull request #23918
- Document secret-resolution execution privileges and SNMP scan exposure Pull request #23923
New smbios_memory collector reports Linux physical memory inventory. Redfish gains BMC logs viewer and hardware enrichment. Legacy alarm notifications now map to Go providers. V2 charts restored.
This week's updates strengthen hardware monitoring and legacy system integration. A new smbios_memory collector provides Linux memory inventory tracking. The Redfish collector gains on-demand BMC logs viewing and expanded hardware details. Most significantly, legacy shell-format alarm notification configurations now map to 23 modern Go providers, enabling smoother migration paths for existing deployments.