Releases: netdata/netdata
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!
v2.8.0
Table of Contents
Release Summary
Netdata v2.8.0 introduces powerful monitoring capabilities and enhanced system visibility alongside continued improvements to stability and reliability.
On the security front, we are proud to announce that Netdata has achieved SOC 2 Type 2 Compliance.
| Highlight | Summary |
|---|---|
| Expanded Chart Analysis | A new UI experience to compare timeframes, correlate metrics, and drill down into dimension values directly from any chart. |
| Netdata AI Improvements | Various enhancements to Netdata AI including the ability to visualize logs within Insights/Investigation views. |
| Expanded Scheduled Reports | Schedule and export full Insights and Investigations views directly to your email, moving beyond simple Dashboards. |
| ServiceNow Integration | Enterprise-grade incident management with direct alerts to ServiceNow. |
| Generic SQL Collector (Alpha) | Monitor any SQL database with custom queries. Define your own metrics for MySQL, PostgreSQL, Oracle, and MS SQL Server. |
| PSS-Based Memory Estimation | More accurate memory tracking for processes using shared memory through intelligent PSS sampling with adaptive prioritization. |
| Stability & Reliability Improvements | Multiple fixes and enhancements to improve system robustness and eliminate potential issues in production environments. |
Release Highlights
News: SOC 2 Type 2 Compliance
Security and trust are paramount at Netdata. We are excited to announce that we have successfully achieved SOC 2 Type 2 compliance.
This certification validates that our internal controls, policies, and procedures regarding security, availability, and confidentiality meet the rigorous standards set by the AICPA. It reflects our ongoing commitment to keeping your data secure.
Expanded Chart Analysis
We have reimagined how you interact with charts to troubleshoot faster with the new Expanded Chart Analysis feature. Below each chart, you will now see an "Expand - Chart Analysis" option.
Clicking this opens a dedicated analysis view offering four powerful tools to dissect your data:
- Compare: Instantly compare the current data against different time periods or baselines (e.g., 24 hours prior, 7 days prior, or custom timeframes) to spot anomalies immediately.
- Correlate: Leverage Netdata AI to automatically find other metrics in your system that correlate with the behavior of the chart you are viewing.
- Drill Down: Explore related metrics and child contexts using Weights Analysis to understand which specific dimensions are driving the spike.
- Chart Values: View raw dimension values and statistical distributions to understand the exact data composition.
Netdata AI Improvements
This release brings various fixes and improvements to Netdata AI, including the ability to visualize logs directly within Insights reports and Investigations.
You can now correlate metrics and logs seamlessly. When viewing a spike in a metric, Netdata AI can analyze and display relevant log lines from that exact timeframe, helping you pinpoint the root cause faster by connecting symptoms (metrics) with evidence (logs).
Netdata AI Scheduled Reports
We have expanded the scope of what you can share with your team. Scheduled Reports are no longer limited to standard Dashboards.
You can now schedule and export full Insights and Investigations views. This allows you to deliver comprehensive, context-rich root cause analyses directly to stakeholders' inboxes, ensuring everyone has the full picture without needing to log in and navigate the UI.
ServiceNow Integration
For enterprise environments, we have added a native ServiceNow integration. You can now route Netdata alerts directly to ServiceNow ITSM, automating incident creation and streamlining your response workflows without custom webhooks or middleware.
Generic SQL Database Monitoring
We're introducing a flexible, configuration-driven SQL collector that lets you monitor any SQL database with custom queries and metrics. This release supports MySQL, PostgreSQL, Oracle, and Microsoft SQL Server.
Important
This is an alpha feature.
Expect rapid improvements and potential configuration format changes in upcoming releases.
What You Get
| Feature | Details |
|---|---|
| Fully Customizable Metrics | Define your own SQL queries and transform results into Netdata charts |
| Multi-Database Support | Works with MySQL/MariaDB, PostgreSQL, Oracle Database, and MS SQL Server using native drivers |
| Flexible Data Mapping | Two result processing modes: Columns mode (map specific columns to dimensions) and KV mode (handle dynamic key-value style results) |
| Per-Row Labels | Create separate chart instances for each row (e.g., per-database, per-table metrics) |
| Status Metrics | Convert state values into binary 0/1 dimensions with conditional rules |
Perfect For
- Custom business KPIs and application-specific metrics
- Database engines not yet covered by dedicated Netdata collectors
- Monitoring internal tables, views, or stored procedure results
- Prototyping metrics before requesting them as built-in collectors
PSS-Based Memory Estimation in apps.plugin
The apps.plugin now provides more accurate memory usage tracking for processes that heavily use shared memory (databases, cache servers, container runtimes) through intelligent PSS (Proportional Set Size) sampling.
Requirements: Linux kernel 4.14 or later. Enabled by default with 5-minute sampling interval—no configuration needed for typical deployments.
Traditional RSS (Resident Set Size) measurements overstate memory usage for processes sharing memory pages. For example, if 10 processes share a 100MB library, RSS would report 1GB total usage when actual consumption is far less.
What's New
| Feature | Details |
|---|---|
| PSS-Based Estimation | Uses Proportional Set Size to divide shared memory fairly among processes, showing true memory footprint in the new app.estimated_mem_usage chart |
| Adaptive Sampling Strategy | Intelligently prioritizes large memory consumers and processes with significant changes, refreshing them within seconds while ens... |
Contributors
Assets 16
v2.7.3
Netdata v2.7.3 is a patch release to address issues discovered since v2.7.2.
This patch release provides the following bug fixes and updates:
- Ensured metrics are properly retained during Journal v2 migration to prevent deletion (#21200, @stelfrag)
- Removed unnecessary
cap_net_bind_servicefrom the otel-plugin to ensure it starts correctly under systemd (#21198, @ilyam8) - Fixed MSSQL chart unit label from “recompiles/” to “recompiles/s” (#21197, @thiagoftsm)
- Changed the alerts API so the summary option is no longer enabled by default (#21192, @stelfrag)
- Initialized CLI earlier during agent startup to support ping, help, and version commands while initializing (#21188, @stelfrag)
- Fixed race condition in ML dimension training and optimized structures for lower memory usage (#21183, @stelfrag)
- Fixed missing
"repeat"field in health dynamic configuration userconfig response (#21181, @ilyam8) - Added periodic data sync on Windows for current data and journal files (#21175, @stelfrag)
- Fixed
/api/v3/datato correctly reportupdate_everyafter filtering, keeping metadata consistent with queried instances (#21170, @ktsaou) - Fixed feature size calculation and added validation in KMeans training to prevent overflows and invalid runs (#21155, @stelfrag)
- Prevented shutdown-time crashes by skipping Sentry breadcrumbs on timeout (#21150, @stelfrag)
- Fixed NaN check in anomaly score calculation (#21149, @stelfrag)
- Added extra safety checks during cgroup discovery to prevent exceeding allocated space (#21148, @stelfrag)
- Reworked maintenance handling by removing the dedicated thread and using the metadata event loop to reduce contention and crashes (#20694, @stelfrag)
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.7.2
Netdata v2.7.2 is a patch release to address issues discovered since v2.7.1.
This patch release provides the following bug fixes and updates:
- Skipped writing the status file on Windows during crashes to prevent deadlocks (#21140, @stelfrag)
- Improved agent startup on Windows by enhancing log-forwarding initialization and thread handling (#21125, @stelfrag)
- Improved disk space calculation in dbengine for Windows systems (#21121, @stelfrag)
- Fixed FreeIPMI crash by unlocking a mutex before scheduled plugin restarts (#21109, @stelfrag)
- Improved SNMP APC device support with detailed sysObjectID mappings and category metadata (#21104, @ilyam8)
- Improved logging and handling of unknown packet IDs by switching to warnings and preventing repeated messages (#21099, @stelfrag)
- Fixed Windows app memory usage reporting to align with Task Manager values (#21090, #21093, @thiagoftsm)
- Registered Netdata in the MCP registry with server information and release action updates (#21088, @ktsaou)
- Improved Windows installer to properly stop the Netdata service and report failures during installation (#21085, @thiagoftsm)
- Fixed memory leak in ACLK HTTPS client by freeing duplicate HTTP response headers (#21084, @ktsaou)
- Fixed disk size calculation in Windows plugin for more accurate mount point free/used values (#21081, #21112, @thiagoftsm)
- Fixed cgroup-network spawn server cleanup to prevent orphaned processes and zombies on fatal exit (#21080, @ktsaou)
- Declared
flatten-serde-jsonat the workspace level to fix duplicate package source issues during packaging (#21072, @vkalintiris) - Added fallback to
/host/for retrieving the machine ID in the OpenTelemetry plugin (#21037, @vkalintiris) - Added remote MCP support with direct HTTP and SSE transport, enabling AI assistants to connect without the nd-mcp bridge (#21036, #21087, @ktsaou)
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.7.1
Netdata v2.7.1 is a patch release to address issues discovered since v2.7.0.
This patch release provides the following bug fixes and updates:
- Add support for old RabbitMQ whoami tags format (#21049, @ilyam8)
- Fix an issue on Windows Agent that does not allow go.d plugin to start (#21068,@stelfrag)
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!