Releases: netdata/netdata
Releases · netdata/netdata
Release list
v2.10.3
Release notes
Netdata v2.10.3 is a patch release to address issues discovered since v2.10.2.
This patch release provides the following bug fixes and updates:
- Fixed a per-PID shared-memory pool leak in
ebpf.pluginthat, on hosts with normal process churn, filled the 32,768-slot pool within ~15 hours and then pegged a CPU core at 100% in an infinite map-iteration loop; aggregation paths now use a non-allocating lookup, freshly-allocated slots are zeroed, module bits are swept on exit, and stale shared-memory and semaphore objects are properly cleaned up on init (#22232, @ktsaou) - Switched the SNMP collector's primary uptime source to
SNMP-FRAMEWORK-MIB::snmpEngineTime(in seconds) to avoid the ~497-day TimeTicks wrap ofhrSystemUptime/sysUpTime, while keeping the existingsystemUptimemetric name and HR-MIB fallback (#22231, @ilyam8) - Split dynamic configuration job-name validation per domain so service discovery, vnode, and secret-store names can include dots (e.g., FQDNs), while collectors retain strict naming rules (#22247, @ilyam8)
- Removed the unused
extra_detailsfield from thego.d/powerstoreHardware struct to fix/hardwareresponse decoding errors that caused job check failures (#22291, @ilyam8)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.10.2
Release notes
Netdata v2.10.2 is a patch release to address issues discovered since v2.10.1.
This patch release provides the following bug fixes and updates:
- Fixed ZFS-related crashes in diskspace.plugin by guarding a NULL filesystem field and replacing the blocking pool-capacity collector with a lightweight cache fed by existing statvfs calls, preventing coredumps on degraded or exporting ZFS pools (#22188, @thiagoftsm)
- Reduced default SNMP MaxOIDs from 60 to 20 for more reliable polling, and removed 32-bit counter fallbacks from the IF-MIB profile to prevent counter type switching and overflow between collection cycles (#22203, @ilyam8)
- Eliminated false-positive "timed out waiting for enable/disable decision" warnings by removing the wait-decision timeout and making the dyncfg command path non-droppable, so back-pressure flows upstream instead of producing 503 errors (#22201, @ilyam8)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.10.1
Release notes
Netdata v2.10.1 is a patch release to address issues discovered since v2.10.0.
This patch release provides the following bug fixes and updates:
- Added
ping_onlyoption to the SNMP collector, allowing collection of only ICMP round-trip time metrics while still using SNMP at startup for device identification and labeling (#22180, @ilyam8) - Fixed SNMP collector retries serialization so a zero value is correctly preserved, and disabled bulk walk detection when MaxRepetitions is set to 0 (#22179, @ilyam8)
- Reduced transient 503 errors on dynamic configuration enable/disable by buffering the command channel and extending the handoff timeout in the go.d plugin (#22183, @ilyam8)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.10.0
Table of Contents
Release Summary
Netdata v2.10.0 introduces secrets management, a Nagios plugins collector, Azure Monitor support, and broad stability improvements.
| Feature | Highlights | Details |
|---|---|---|
| Secrets Management | 4 resolver types, 4 backends | • Environment variables, files, commands, and secretstore references • AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, HashiCorp Vault |
| Enhanced AI Conversations | Reports and Alerts integration | • Resume and expand generated AI reports • Ask AI about active alerts or charts, their root causes, and recommended remediation steps |
| Advanced Alerting | Silencing, Evaluation & Acknowledge | • Complete support for recurrence rules for Alerts Silencing • Test alert definitions against historical data before deploying • Acknowledge alerts you're working on |
| Improved Custom Dashboards | Complete Customisation | • Add Metrics, Logs, Events, Node List, Alerts, Live Functions and Text components • Duplicate Custom Dashboards |
| Nagios Plugins Collector | Run any Nagios-compatible check | • Automatic performance data charts • Threshold-based alerting with soft/hard state logic • Execution metrics (duration, CPU, memory) |
| Azure Monitor Collector | 38 service profiles, 1,300+ metrics | • Automatic resource discovery via Azure Resource Graph • Multi-subscription, flexible scoping by resource groups/regions/tags |
| Azure AD for Database Collectors | MSSQL, PostgreSQL, Generic SQL | • Service principal, managed identity, and default credential chain • Passwordless auth for Azure-hosted databases |
| New Storage Collectors | Dell PowerStore, Dell PowerVault | • Hardware health, performance, capacity, and sensor monitoring • Built on V2 collector framework |
| Expanded Collector Coverage | vSphere, MSSQL, SNMP, Docker | • vSphere datastores/clusters/resource pools • MSSQL Always On AG monitoring • SNMP IPSec/VPN profiles for FortiGate, Juniper, MikroTik, Check Point • Docker container listing function |
| OpenTelemetry Improvements | Metrics pipeline overhaul | • Proper slot-based aggregation with configurable intervals • Multi-slot ingestion with out-of-order support |
| Stability & Performance | Production reliability | • Faster agent startup • ML prediction optimization • Alerts API speedup • Multiple crash and race condition fixes |
Release Highlights
Secrets Management
Keep collector credentials out of plain-text configuration files. Netdata now lets you reference secrets in collector configurations instead of storing them directly. Passwords, tokens, and API keys are resolved at runtim...
Contributors
kiwixz and DarkByteZero
Assets 16
v2.9.0
Table of Contents
Release Summary
Netdata v2.9.0 brings powerful database observability and expanded OpenTelemetry support.
| Feature | Highlights | Details |
|---|---|---|
| Interactive Query Analysis | 14+ databases supported | • Identify slow queries • Debug bottlenecks • Monitor operations • No manual database connections required |
| Rebuilt SQL Server Collector | Rewritten in Go | • Comprehensive metrics • Query Store integration • UI-based configuration |
| OpenTelemetry Log Ingestion | Logs via otel plugin |
• Stored in systemd-compatible journal files • Configurable retention policies |
| Stability Improvements | Production reliability | • Under-the-hood fixes for more robust operation |
Release Highlights
New Top Tab Functions: 14+ Databases and SNMP
We've added interactive query analysis functions to database collectors, letting you identify slow queries, long-running operations, and performance bottlenecks directly from the Netdata
dashboard—no need to connect to the database and run diagnostic queries manually.
| Database | Functions | Description |
|---|---|---|
| ClickHouse | Top Queries | • Aggregated query stats from system.query_log• Execution time, memory usage, rows read/written |
| CockroachDB | Top Queries | • Statement statistics from crdb_internal• Execution counts, latency, rows processed |
| Running Queries | • Currently executing statements via SHOW CLUSTER STATEMENTS• Client info, duration, distributed execution status |
|
| Couchbase | Top Queries | • Completed N1QL requests from system:completed_requests• Service time, result count, error tracking |
| Elasticsearch/OpenSearch | Top Queries | • Active search tasks from Tasks API • Running time, search type, node distribution |
| MongoDB | Top Queries | • Slow operations from system.profile• Execution time, docs examined, keys examined, plan summary |
| MS SQL Server | Top Queries | • Query Store statistics • CPU time, logical reads/writes, memory grants, parallelism |
| Deadlock Info | • Latest deadlock from system_health Extended Events• Victim process, lock mode, wait resource |
|
| Error Info | • Recent SQL errors from Extended Events session • Error number, message, query text |
|
| MySQL/MariaDB | Top Queries | • Digest statistics from performance_schema• Execution time, lock time, rows examined/sent |
| Deadlock Info | • Latest InnoDB deadlock from SHOW ENGINE INNODB STATUS• Victim transaction, lock mode, wait resource |
|
| Error Info | • Recent SQL errors from Performance Schema history • Error number, SQLSTATE, message per query digest |
|
| Oracle DB | Top Queries | • SQL statistics from V$SQLSTATS• CPU time, elapsed time, buffer gets, disk reads |
| Running Queries | • Active sessions from V$SESSION• Wait events, blocking sessions, SQL text |
|
| PostgreSQL | Top Queries | • Statement statistics from pg_stat_statements• Total/mean time, shared blocks hit/read, temp blocks |
| Running Queries | • Active queries from pg_stat_activity• Duration, wait events, client info, backend state |
|
| ProxySQL | Top Queries | • Query digest from stats_mysql_query_digest• Execution time, rows affected/sent, errors |
| Redis | Top Queries | • Slow commands from SLOWLOG• Command name, duration, client info |
| RethinkDB | Running Queries | • Active jobs from rethinkdb.jobs• Query text, duration, involved servers |
| YugabyteDB | Top Queries | • YSQL statistics from pg_stat_statements• Execution time, calls, rows processed |
| Running Queries | • Active backends from pg_stat_activity• Query state, wait events, elapsed time |
|
| Generic SQL | User-Defined | • Custom SQL functions defined in job configuration • Interactive table views in Top tab for any SQL database |
What You Can Do:
- Identify resource hogs: Sort by total execution time, CPU time, or I/O
- Spot frequent queries: Find high-call-count queries that may benefit from caching
- Debug in real-time: See currently running queries and which client initiated them
- No extra tools needed: All analysis happens in the Netdata dashboard's Top tab
Important
Some functions require database-specific configuration (e.g., enabling Query Store, pg_stat_statements, or profiling).
See each collector's documentation for prerequisites.
Also Added: SNMP Network Interfaces Function
| Collector | Function | Description |
|---|---|---|
| SNMP | Network Interfaces | • Real-time interfa... |
v2.8.5
Netdata v2.8.5 is a patch release to address issues discovered since v2.8.4.
This patch release provides the following bug fixes and updates:
- Updated the Netdata Docker image to Debian 13.3 with the latest upstream updates and security fixes
- Standardized alert configuration to use a consistent type for time group values (#21528, @ilyam8)
- Fixed CSV parser configuration serialization so empty settings are correctly omitted from logs configuration output (#21526, @ilyam8)
- Fixed ProxySQL backend status metrics in the go.d collector to correctly reflect reported backend states (#21524, @ilyam8)
- Fixed proc file parsing to support non-seekable files, restoring network stats collection on affected kernels (#21507, @ilyam8)
- Fixed edit-config to ignore inherited container environment values, preventing incorrect command handling (#21505, @ilyam8)
- Fixed vnode label configuration by allowing arbitrary label keys in the go.d schema, enabling labels to be set via the UI (#21503, @ilyam8)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.8.4
Netdata v2.8.4 is a patch release to address issues discovered since v2.8.3.
This patch release provides the following bug fixes and updates:
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.8.3
Netdata v2.8.3 is a patch release to address issues discovered since v2.8.2.
This patch release provides the following bug fixes and updates:
- Fixed the go.d AP collector to handle unknown station statistics gracefully (#21461, @ilyam8)
- Fixed incorrect plugin and binary paths on Windows for the go.d plugin by correctly detecting the installation prefix at startup (#21451, @ilyam8)
- Improved go.d job management by avoiding blocking during job shutdown, keeping other jobs responsive (#21448, @ilyam8)
- Fixed and standardized Windows AD, ADCS, and ADFS charts, and improved stability and accuracy of Windows hardware metrics collection (#21433, #21454, @thiagoftsm)
- Fixed SNMP service discovery by accepting version “2” and using the default polling interval instead of overriding it (#21424, @ilyam8)
- Logged data collection duration when go.d collections are skipped due to a previous run still in progress (#21423, #21425, @ilyam8)
- Fixed the MSSQL errors chart in the Windows plugin by using the correct metric (#21412, @thiagoftsm)
- Removed the strict
rabbitmq_versioncheck to improve RabbitMQ collector compatibility with older brokers (#21411, @ilyam8) - Added collection statistics to the SNMP go.d collector and exposed them as per-profile charts (#21409, @ilyam8)
- Updated ndexec runner to return captured stdout on command failures (#21405, @ilyam8)
- Disabled the MongoDB exporter on affected Ubuntu versions due to insecure libbson dependencies (#21403, @Ferroin)
- Updated bundled components used in static builds (#21401, @Ferroin)
- Fixed off-by-one validation in Journal v2 by treating
extent_index == extent_entriesas invalid, preventing out-of-bounds access (#21400, @stelfrag) - Fixed timed waits in completion to handle spurious wakeups and honor shutdown timeouts, preventing premature timeouts and hangs (#21395, @stelfrag)
- Prevented datafiles from exceeding their max size by making size checks atomic and accounting for incoming writes (#21390, @stelfrag)
- Updated DEB package builds to use XZ or zstd compression instead of gzip (#21310, @Ferroin)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.8.2
Netdata v2.8.2 is a patch release to address issues discovered since v2.8.1.
This patch release provides the following bug fixes and updates:
- Adjusted Windows sensors initialization by moving COM and Sensor API setup into the sensors thread for better stability (#21374, @stelfrag)
- Replaced dots with slashes in OTEL metric families to enable hierarchical grouping in dashboards (#21371, @ilyam8)
- Fixed user group updates to ensure proper Proxmox group assignment in Docker entrypoint (#21364, @ilyam8)
- Ensured Netdata has access to NVIDIA device files by adding the netdata user to the appropriate group, fixing GPU monitoring on non-Debian systems (#21358, #21359, @ilyam8)
- Prevented replication from stalling by detecting empty-response loops and safely completing the process (#21357, @stelfrag)
- Stopped replication when the parent is already caught up, preventing stalls and unnecessary gap-filling (#21352, @stelfrag)
- Prioritized environment-provided config directories in go.d for runtime overrides (#21345, @ilyam8)
- Silenced Redis client library logs in the go.d Redis collector to reduce noise (#21344, @ilyam8)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.8.1
Netdata v2.8.1 is a patch release to address issues discovered since v2.8.0.
This patch release provides the following bug fixes and updates:
- Fixed issue where vnodes created through dynamic configuration would disappear after agent restart (#21332, @ilyam8)
- Disabled PSS memory sampling in apps.plugin by default to reduce CPU overhead (#21330, @ilyam8)
- Added source unit field to alert values to display the original metric unit used in expressions (#21326, @ilyam8)
- Removed noisy INFO log from Windows datafile sync to reduce log spam during periodic syncs (#21325, @stelfrag)
- Fixed compilation when dbengine is disabled (#21323, @stelfrag)
- Improved Podman container name resolution in cgroups plugin by correctly extracting container IDs from libpod-conmon paths (#21317, @ilyam8)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!