Netdata: download ældre versioner

NOTICE
The v2.12.0 build of the Netdata Agent has been discovered to have serious stability issues that cause it to crash randomly on startup due to an upstream bug in some of the tooling we depend on. As such, we have removed the installer for it from the release page. A fix is expected in v2.12.1, but until that release, users are encouraged to use the latest known working version (v2.11.1), which can be downloaded here.
Table of Contents
- Summary
- Highlights
- OpenTelemetry Traces, in Early Access
- Redfish: Out-of-Band Server Hardware Monitoring
- SNMP Topology: Diagnostics, Offline Triage and Replay
- New Collectors: S3 Object Storage and SMBIOS Memory
- Ceph, Reworked as a Prometheus Complement
- Windows: Hyper-V, RDP and Broader Coverage
- Secrets and Privilege Hardening in go.d
- Query Engine: Correctness and Faster Weights
- Agent Stability: dbengine, SQLite, ACLK and ML
- Netdata Cloud: Infrastructure Knowledge, Node Decommissioning and AI Conversations
- Platform Support Changes
- Acknowledgments
- Contributions
- Collectors
- Packaging/Installation
- Documentation
- Other Notable Changes
- Deprecation notice
- Support options
Release Summary
v2.11.0 brought network topology and made logs a first-class signal next to metrics. v2.12.0 adds OpenTelemetry
traces, out-of-band hardware monitoring through Redfish, and a diagnostics layer that makes SNMP topology debuggable,
alongside a large round of collector, query and stability fixes.
The third observability signal arrives. Netdata already ingested OpenTelemetry metrics and logs. This release adds
traces: OTLP trace records are received, normalized and stored by the agent under their own retention policy, with a
purpose-built columnar store — trace-aware indexes, bloom filters and rollups — and an otel-traces query Function that
searches traces, aggregates them over a window and drives an overview heatmap. You explore them in a new Traces tab
of the dashboard, available today as an Early Access feature.
Hardware monitoring goes out-of-band. The new Redfish collector talks to the BMC — iDRAC, iLO and any
DMTF Redfish implementation — rather than to the operating system, so as long as the BMC stays powered and reachable it
keeps reporting fans, temperatures, power supplies, drives and controllers when the host itself is unhealthy, rebooting or
powered down. It ships with sensor and hardware
inventory Functions, independent per-sensor threshold health, and an on-demand BMC log viewer. Alongside it,
SMBIOS Memory compares the firmware's per-slot memory inventory with an accepted baseline and raises an alert when a
recorded DIMM goes missing or comes back smaller — memory loss that a total-RAM figure alone does not pin to a slot.
The network work from v2.11.0 becomes operable. The SNMP topology engine gained an entire diagnostics layer: every
walk records its timing, its profile decisions and its failures; the evidence is retained in bounded form, published
independently of whether topology collection succeeded, packaged into a portable archive, and folded into the agent's
support bundle. A topology graph can then be replayed hermetically from that archive and inspected offline, which turns
"SNMP topology is not seeing this switch" from a site visit into a file you can send us. LLDP-V2 for PAN-OS, Meraki L2,
IpAddressTable support and a set of reusable topology-role profiles widen what the engine can see in the first place.
In Netdata Cloud, Netdata AI learns your infrastructure. With Infrastructure Knowledge, your team writes down
what only it knows — which services matter, what is expected, what normal looks like — and Netdata AI remembers facts
you tell it in conversation, then reads both before every conversation, investigation and report. AI conversations now
survive a closed tab and no longer fail when they grow long, and nodes being retired can be decommissioned so they
stop sending notifications.
And a lot of the release is consolidation. The Ceph collector was re

Table of Contents
- Summary
- Highlights
- Network Monitor Dashboard (Technical Preview)
- Network Flows: NetFlow, IPFIX and sFlow (Technical Preview)
- Network Topology and Application Dependencies (Technical Preview)
- SNMP Trap Listener
- Expanded SNMP Device Coverage
- Logs: OpenTelemetry Ingestion and a Unified Log Engine
- AWS CloudWatch Collector
- New Collectors
- Endpoint Monitoring: macOS, Windows, FreeBSD and Linux
- Prometheus Collector Overhaul
- Query Engine and API
- Netdata Cloud: AI Troubleshooting and MCP
- Netdata Cloud: Alerts and Notifications
- Netdata Cloud: Fleet Management and Scale
- Netdata Cloud: Dashboards and Charts
- Security Hardening
- End of Full Support for RHEL 7.x, CentOS 7.x, and Amazon Linux 2
- Acknowledgments
- Contributions
- Collectors
- Packaging/Installation
- Documentation
- Other Notable Changes
- Deprecation notice
- Support options
Release Summary
Netdata has always been exceptionally good at one particular thing: telling you, per second and with no configuration,
what is happening inside a machine. v2.11.0 is the release where that stops being the boundary.
Two things happen here, and together they change what Netdata is.
First, Netdata learns the network. A new Network Monitor dashboard brings device inventory, metrics, topology,
flows, traps and alerts into one place. Behind it, Network Flows receives NetFlow, IPFIX and sFlow from your routers,
switches and firewalls and turns raw records into a faceted view of who is talking to whom. Network Topology walks
your devices over SNMP and draws the Layer 2 and Layer 3 map — LLDP neighbours, forwarding databases, OSPF and BGP
adjacencies — while Application Dependency Mapping does the same for your software, reading your Linux hosts'
kernels to map what each process, container and Kubernetes workload talks to, with nothing to instrument. The SNMP Trap
Listener makes Netdata a trap receiver that decodes traps from 800+ vendor profiles into
charts and readable messages instead of raw OIDs. Feeding all of it, SNMP device coverage grew from 229 to 273
profiles. The usual Netdata rules still apply: the profiles are already written, collection and storage stay on your own
infrastructure, and there is little to configure beyond telling Netdata where the devices are. Network Monitor, Network
Flows and Network Topology ship as technical previews — complete enough to run today, open to every Netdata user
while in preview, and still moving fast.
Second, and just as important, logs become a first-class pillar of the platform. This release adds OpenTelemetry
logs — OTLP log records are ingested, stored and queried from the same Logs tab that already serves systemd journal
and Windows events, with journald, filelog and syslog receivers, configurable retention, log-to-metric conversion
and parsing for unstructured lines. The deeper change is architectural: the same faceted, high-cardinality log engine now
backs systemd journal, Windows events, OpenTelemetry logs, SNMP traps and network flows alike. Five very different
signal types, one query surface, all stored on your own infrastructure.
Around those two, this release completes the major-cloud set with a new AWS CloudWatch collector — the counterpart to
the Azure Monitor collector added in v2.10.0 — and rebuilds the Prometheus collector around a real relabeling engine
with application profiles. Underneath all of it sits the largest stability and memory-safety effort we have ever shipped
in a single release: 87 incremental parts across the database engine, streaming, ACLK, health, ML and libnetdata.
Netdata's strong endpoint monitoring capabilities have been enhanced. macOS monitoring was rebuilt natively: unified
logs through Apple's OSLog framework, GPU, SMC and IOHID sensors, fans, power and battery, thermal pressure and NVMe
health, none of which was reachable before without dropping to log show and powermetrics by hand. Windows added
Active Directory and SMB monitoring on a reworked perflib