Releases: netdata/netdata
v2.3.2
Netdata v2.3.2 is a patch release to address issues discovered since v2.3.1.
This patch release provides the following bug fixes and updates:
- Fixed journal file creation reliability with improved error handling and simplified allocation process (#20018, @ktsaou)
- Fixed leakage of build environment identifiers by blacklisting GitHub runner machine IDs (#20016, @ktsaou)
- Fixed potential memory access violations by adding validation for journal file headers and page boundaries (#20013, @stelfrag)
- Fixed a rare crash condition by properly reinitializing data collection for obsolete or archived dimensions (#20007, @ktsaou)
- Fixed MegaCLI collector to properly handle missing battery backup units (#20008, @ilyam8)
- Changed UUID generation to use version 4 format for better uniqueness (#20002, @ktsaou)
- Added detection for additional CI environment variables to automatically disable telemetry (#19999, @ktsaou)
- Fixed Agent status system to handle null UUIDs and improved tracking of shutdown time, crash counts, and connection states (#19996, #20003, #20011 @ktsaou)
- Added detailed worker thread status information and enhanced crash diagnostics capabilities (#19992, @ktsaou)
- Fixed potential crash in Windows perflib collector when handling null pointers (#19985, @ktsaou)
- Fixed error reporting to preserve errno values during out-of-memory conditions (#19984, @ktsaou)
- Fixed potential crashes when handling empty data arrays (#19983, @ktsaou)
- Fixed Agent shutdown by properly joining ACLK and metadata threads before closing database connections (#19980, @stelfrag)
- Fixed random crashes during shutdown by avoiding precompiled database statements for host metadata (#19978, @stelfrag)
- Limited maximum database file size to 1GB to optimize memory usage during file operations (#19977, @stelfrag)
- Fixed crash in variable lookup function when processing search results with scores (#19972, @ktsaou)
- Fixed ACLK synchronization thread shutdown with better termination sequence and timeout handling for stuck operations (#19966, @stelfrag)
- Improved Parent node startup performance by preloading UUIDs into metrics registry for faster initialization (#19964, @ktsaou)
- Fixed Windows installer to properly manage configuration files and handle upgrades correctly (#19962, @thiagoftsm)
- Fixed potential crash in health alarm cleanup when unlinking alerts from charts (#19956, @stelfrag)
- Fixed buffer overflow when processing cloud rooms during Agent claiming on startup (#19954, @stelfrag)
- Updated Agent status reporting system with enhanced crash diagnostics, anonymized stack traces, and ACLK connection status tracking (#19953, #19957, #19959 @ktsaou)
- Fixed thread creation issues by adding retry logic when system resource limits are temporarily reached (#19951, @stelfrag)
- Added monitoring of IIS Application Pool metrics to Windows collector (#19950, @thiagoftsm)
- Improved metadata thread stability with better shutdown handling and enhanced event loop management (#19929, @stelfrag)
- Fixed potential deadlocks by processing alert configuration database operations asynchronously through the metadata thread (#19885, @stelfrag)
- Reworked shared memory management in eBPF plugin for more reliable interprocess communication (#19844, @thiagoftsm)
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.3.1
Netdata v2.3.1 is a patch release to address issues discovered since v2.3.0.
This patch release provides the following bug fixes and updates:
- Fixed debug information handling by including it in default builds while disabling separate debuginfo packages for Debian-based distributions (#19946, #19948 @Ferroin)
- Fixed static build configuration to avoid unnecessary libunwind compilation (#19939, @Ferroin)
- Improved detection of low memory conditions with more aggressive monitoring (#19938, @ktsaou)
- Fixed installation path for updater script crontab configuration (#19935, @ralphm)
- Fixed validation of database page size limits for 32-bit compression format (#19932, @stelfrag)
- Fixed compilation issues when building without database engine support or with address sanitizer enabled (#19930, @stelfrag)
- Added additional system resource metrics to status file including memory usage and enhanced out-of-memory protection information (#19928, #19937 @ktsaou)
- Fixed security issue by preventing exposure of absolute file paths in web server responses (#19925, @ktsaou)
- Fixed security vulnerability in daemon status file handling by using file descriptor-based permissions to prevent race conditions (#19924, @Ferroin)
- Removed insecure SVG generation endpoint to prevent potential code injection vulnerabilities (#19919, @ilyam8)
- Fixed unaligned memory access in socket message buffer by properly aligning memory structures (#19917, @vkalintiris)
- Fixed ACLK synchronization by ensuring thread initialization completes before proceeding with startup (#19916, @stelfrag)
- Fixed issue where commands could be queued before ACLK initialization was complete (#19914, @ktsaou)
- Fixed potential crash when database engine encounters null data files during range operations (#19913, @ktsaou)
- Fixed Agent status reporting to handle first-run scenarios when no previous status file exists (#19912, @ktsaou)
- Added initial implementation of libbacktrace for improved crash diagnostics (#19910, @ktsaou)
- Fixed reliability calculation to properly handle normal Agent exit cases (#19909, @ktsaou)
- Added enhanced shutdown diagnostics with timeouts and improved system information in crash reports including cloud provider details (#19903, @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.3.0
Table of Contents
Netdata Growth
- 1.5 million downloads per day
- 73.7k GitHub stars!
- 656.1M Docker Hub pulls!
Netdata continues to experience phenomenal growth, with over 1.5 million downloads daily through Cloudflare and Docker Hub, fueling user observability worldwide.
Thanks to your unwavering support ❤️, Netdata is the leader in the observability category in the CNCF landscape, ahead of all other solutions, including Elasticsearch, Grafana, and Prometheus, in GitHub stars. This demonstrates the trust and admiration of our community.
This success drives rapid adoption among enterprises, reflecting the growing recognition of Netdata as the go-to observability solution for both cloud-native and on-premises environments. Our commitment remains steadfast: to deliver cutting-edge, AI-powered observability with unmatched performance and simplicity—all while being significantly more affordable.
We are also proud to see our users and customers experience high-scale setups, achieving reliable multi-million samples/s setups, effortlessly, streamlining their operations with Netdata.
As we evolve, our focus on empowering businesses with higher-fidelity AI insights ensures Netdata remains the easiest and fastest way to optimize infrastructure and applications at any scale. 🚀
Do you like Netdata? Give Netdata a ⭐ too, on GitHub!
Release Summary
Netdata 2.3 delivers significant enhancements to monitoring reliability and scalability:
- Crash Handling & Reporting: A zero-sampling system that captures and analyzes agent crashes with complete diagnostic information, significantly improving reliability across diverse environments.
- Extreme Cardinality Protection: Automatic safeguards that maintain performance in high-scale environments with millions of time series while intelligently managing metadata retention.
- Nodes Ephemerality & Streaming Alerts: A sophisticated approach to handling node connections in distributed environments, reducing alert noise by distinguishing between permanent and ephemeral nodes.
- SNMP Service Discovery: A new system automatically finds and monitors SNMP-enabled devices on configured networks, eliminating manual configuration.
Release Highlights
Nodes Ephemerality & Streaming Alerts
Netdata 2.3 implements a more sophisticated approach to handling node connections in distributed environments. We now define ephemeral nodes as "nodes that are expected to disconnect without raising alerts", enabling smarter monitoring of dynamic infrastructure.
| Feature | Description |
|---|---|
| Smart Node Classification | Distinguish between permanent infrastructure (servers) and ephemeral resources (containers, auto-scaling instances) |
| Targeted Alerting | Disconnection alerts trigger only for permanent nodes, reducing alert noise and focusing attention on genuine issues |
| Dynamic Infrastructure Support | Configure auto-scaling cloud instances, containers, and test environments as ephemeral to prevent unnecessary alerts |
| Simple Configuration | Mark nodes as ephemeral with a single setting in netdata.conf: is ephemeral node = yes |
| Automated Cleanup | Configurable retention periods to automatically remove disconnected ephemeral nodes from dashboards |
| Selective Cloud Notifications | Netdata Cloud now sends node-unreachable notifications exclusively for permanent nodes |
| Node Management CLI | Use netdatacli mark-stale-nodes-ephemeral to clear alerts for permanently offline nodes |
Learn more about managing ephemeral nodes.
Extreme Cardinality Protection
Netdata 2.3 introduces automatic protection against extreme cardinality issues when combining high-dimensional metrics with long retention periods. This system:
| Feature | Description |
|---|---|
| Intelligent Detection | Automatically identifies contexts with excessive ephemeral metrics (≥1000 instances with >50% ephemerality) |
| Balanced Protection | Preserves all actively collected metrics while selectively clearing retention for ephemeral ones |
| Resource Optimization | Prevents memory bloat and performance degradation from abandoned time-series metadata |
| Configurable Thresholds | Adjustable settings for instance count and ephemerality percentage to match your environment |
| Transparent Operation | Detailed logging of all protection activities for easy monitoring and verification |
This protection maintains Netdata's performance even in high-scale environments with millions of time series, while still allowing unlimited cardinality for high-resolution data. Learn more about configuring this feature.
Crash Handling & Reporting
We've implemented a powerful, zero-sampling crash monitoring system that captures and analyzes agent restarts and crashes with complete diagnostic information. This solution leverages systemd's journal for flexible, scalable event tracking without additional licensing costs. With anonymous telemetry enabled, this system helps us identify critical issues across diverse environments, significantly improving Netdata's reliability for all users. Read more about our approach in this blog post.
| Feature | Description |
|---|---|
| Zero-Sampling Collection | Captures every single crash event without sampling, providing complete visibility into system behavior |
| Comprehensive Diagnostics | Records detailed stack traces, error messages, and system context for accurate root cause analysis |
| Efficient Deduplication | Intelligent system that prevents redundant reporting (only one crash type per agent per day) |
| Privacy-Focused | No IP addresses collected, only anonymous telemetry with user opt-out option |
| Lightweight Implementation | Minimal performance impact, only activates when Agent starts, stops, or crashes |
| Cost-Effective Architecture | Leverages existing systemd journal infrastructure instead of expensive third-party solutions |
| High Scalability | Processes up to 20,000 events per second per instance with horizontal scaling capability |
| Flexible Analysis | Transforms complex JSON data into flattened journal entries for powerful filtering and correlation |
| Proven Results | Already identified and resolved dozens of critical issues across diverse environments |
SNMP Discovery
Netdata 2.3 adds an SNMP service discovery system that automatically finds and monitors SNMP-enabled devices on your networks.
| Feature | Description |
|---|---|
| Automated Device Detection | Scans configured networks to discover SNMP-enabled devices without manual configuration |
| Flexible Network Configuration | Supports various IP range formats including single IPs, ranges, and CIDR notation (up to 512 IPs per subnet) |
| Customizable Credentials | Configure multiple credential sets with support for SNMPv2c and SNMPv3 with various security levels |
| Performance Optimization | Controls network impact through concurrent scan limits and configurable caching of discovery results |
| Seamless Integration | Automatically... |
Contributors
Assets 18
v2.2.6
Netdata v2.2.6 is a patch release to address issues discovered since v2.2.5.
This patch release provides the following bug fixes and updates:
- Fixed log2journal to properly handle empty JSON arrays and objects in log parsing (#19685, @ktsaou)
- Fixed MariaDB collector to handle CPU time values reported in microseconds since version 10.11.11 (#19683, @ilyam8)
- Added user action logging to dyncfg while ensuring sensitive information is hidden when dashboard is in anonymous mode (#19674, @ktsaou)
- Disabled legacy Go sensors collector in preparation for removal, as metrics are now collected by the C implementation (#19667, @ilyam8)
- Added user action logging to go.d.plugin dyncfg (#19666, #19672, #19673, #19676 @ilyam8)
- Added periodic event loop processing to prevent database engine starvation (#19661, @ktsaou)
- Added deployment metrics collection to KubeState collector, including replica status and availability alerts (#19657, #19662, #19664 @ilyam8)
- Added agent timezone information to host labels (#19656, @ktsaou)
- Added fallback to standard memory allocation when onewayalloc allocator fails (#19646, @ktsaou)
- Fixed Windows log collection to append new fields instead of renumbering them (#19640, @ktsaou)
- Improved error handling in Windows perflib collector to be more robust (#19631, @ktsaou)
- Prevented Sentry report flooding during database initialization failures (#19628, @ktsaou)
- Added a new alert to detect system reboots (#19624, @ilyam8)
- Fixed SSL certificate handling in statically linked libcurl by properly configuring certificate paths during build (#19622, @ktsaou)
- Added additional context information to Sentry crash reports for better debugging (#19608, @vkalintiris)
- Added automatic detection of system DNS servers from /etc/resolv.conf in DNS query collector (#19562, @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.2.5
Netdata v2.2.5 is a patch release to address issues discovered since v2.2.4.
This patch release provides the following bug fixes and updates:
- Fixed MariaDB collector to handle CPU time values reported in microseconds since version 11.4.5 (#19618, @ilyam8)
- Changed clickhouse_replicated_readonly_tables info to clarify read-only state conditions for replicated tables (#19616, @ilyam8)
- Fixed indirect cloud access to function properly when an Agent is claimed but temporarily offline by using Parent's claim ID (#19611, @ktsaou)
- Added data interpolation to median and percentile calculations in the stats.d plugin (#19606, @ktsaou)
- Fixed potential database access issues during shutdown by properly closing the database when startup errors occur (#19600, @stelfrag)
- Fixed a memory corruption issue by properly dequeuing contexts from hub before deletion (#19599, @ktsaou)
- Fixed various issues in journal watcher, including improved event parsing, corrected path handling, and resolved memory-related bugs (#19592, @ktsaou)
- Fixed NVMe device discovery to properly handle device paths in nvme-cli v2.11 (#19577, @ilyam8)
- Fixed MySQL collector to properly respect the global variables refresh interval instead of collecting them on every iteration (#19549, @arkamar)
- Fixed several CI/build system issues, including static build conditions, POWER8+ build hosts, Ubuntu runner versions, and compiler flags (#19575, #19579, #19614, #19619, @Ferroin)
- Fixed Amazon Linux aarch64 package builds by migrating to GitHub's ARM CI runners (#19427, @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.2.4
Netdata v2.2.4 is a patch release to address issues discovered since v2.2.3.
This patch release provides the following bug fixes and updates:
- Fixed go.d plugin to properly clean up charts for stopped and removed jobs to prevent stale alerts (#19573, @ilyam8)
- Fixed a memory leak in the health component (#19569, @stelfrag)
- Added a new agent status to indicate when connection to the Cloud is in progress (#19564, @stelfrag)
- Fixed Windows collector to properly monitor multiple MSSQL instances running simultaneously (#19559, @thiagoftsm)
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.2.3
Netdata v2.2.3 is a patch release to address issues discovered since v2.2.2.
This patch release provides the following bug fixes and updates:
- Fixed an issue with newly created and claimed agents not immediately appearing in the cloud (#19542 @stelfrag)
- Fixed database engine to properly handle files larger than 4GB by correcting 32-bit variable limitations (#19538, #19539 @ktsaou)
- Fixed an issue where contexts remained in a non-live state after child reconnections due to incorrectly cached collection flags (#19536 @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.2.2
Netdata v2.2.2 is a patch release to address issues discovered since v2.2.1.
This patch release provides the following bug fixes and updates:
- Fixed a memory corruption issue that occurred when streaming remote functions failed (#19532 @ktsaou)
- Fixed detection of Microsoft SQL Server named instances in the Windows MSSQL collector (#19527 @thiagoftsm)
- Fixed an issue where receiver connections were terminated when sender encountered socket errors, while also optimizing data collection performance (#19524 @ktsaou)
- Simplified eBPF plugin dependencies by linking directly to libbpf instead of through libnetdata (#19514 @Ferroin)
- Removed unnecessary lm_sensors dependency from Go plugin in RPM packages (#19511 @k0ste)
- Fixed URL-encoded proxy credentials handling in ACLK to properly decode usernames and passwords containing special characters (#19508 @ktsaou)
- Fixed alert transition timing to use a 10-second delay for state changes to removed and to correctly use the alert trigger timestamp for cloud notifications (#19507 @stelfrag)
- Improved buildinfo output (-W buildinfo) to include additional plugins and compiler flag information for better troubleshooting support (#19506, #19513 @ktsaou)
- Fixed NVMe device discovery to support the new output format introduced in nvme-cli v2.11 (#19505 @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.2.1
Netdata v2.2.1 is a patch release to address issues discovered since v2.2.0.
This patch release provides the following bug fixes and updates:
- Fixed tables showing incorrect positive values for negative metrics (#19496, #19497 @ktsaou)
- Added
ifb4*to default network interface exclusion patterns of proc.plugin (#19494, @intelfx) - Removed obsolete ZFS pool state configuration option (#19491, @intelfx)
- Improved alert processing performance through optimized SQL operations and improved transition checksg (#19489, @stelfrag)
- Improved performance when compiled with LTO enabled (#19488, @ktsaou)
- Improved alert transition processing performance by using precompiled SQL statements (#19487, @stelfrag)
- Fixed issues identified by Coverity code analysis (#19484, @ktsaou)
- Added system information, Agent name and version to Netdata-streaming function (#19482, #19485 @ktsaou)
- Changed ping plugin's privileged option to true by default for dynamic configuration jobs (#19480, @ilyam8)
- Fixed high CPU usage in privileged ping collector by updating pro-bing library to 0.6.0 (#19477
- Improved performance by optimizing host status checks and ingestion status queries (#19472, @ktsaou)
- Improved stale node cleanup performance by moving
netdatacli remote-stale-nodeprocessing to a worker thread (#19471, @stelfrag) - Fixed a crash that occurred during virtual nodes cleanup when receiver is not present (#19467, @ktsaou)
- Fixed unnecessary health alerts by ensuring child nodes complete replication before initializing health checks (#19463, @stelfrag)
- Improved ACLK memory management by implementing ARAL allocator for command queuing (#19459, @stelfrag)
- Added Pulse metrics for parent node to improve stream health monitoring (#19445, #19466 @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.2.0
Table of Contents
Netdata Growth
- 1.5 million downloads per day
- 73k GitHub stars!
- 653M Docker Hub pulls!
Netdata continues to experience phenomenal growth, with over 1.5 million downloads daily through Cloudflare and Docker Hub, fueling observability for users worldwide.
Thanks to your unwavering support ❤️, Netdata is the leader in the observability category in the CNCF landscape, ahead of all other solutions including Elasticsearch, Grafana, and Prometheus in GitHub stars, showcasing the trust and admiration of our community.
This success is driving rapid adoption among enterprises, reflecting the growing recognition of Netdata as the go-to observability solution for both cloud-native and on-premises environments. Our commitment remains steadfast: to deliver cutting-edge, AI-powered observability with unmatched performance and simplicity—all while being significantly more affordable.
As we evolve, our focus on empowering businesses with higher-fidelity AI insights ensures Netdata remains the easiest and fastest way to optimize infrastructure and applications at any scale. 🚀
You like Netdata? Give Netdata a ⭐ too, on GitHub!
Release Summary
Netdata 2.2.0 delivers major performance optimizations targeting Parent-to-Parent streaming deployments, achieving 50% less memory usage across all installations, while Parent nodes streaming to other Parents benefit from 50% reduced bandwidth usage and 20% lower CPU utilization.
New auto-detected configuration profiles optimize performance for different use cases: Parent, Child, and IoT deployments.
Release Highlights
Performance and Scalability Improvements
| Area | Improvement | Technical Details |
|---|---|---|
| Memory Management | 50% reduction in memory usage (all deployments) | Eliminated majority of memory fragmentation by separating long-standing data from ephemeral data using specialized allocation algorithms. Enhanced out-of-memory protection allows cache shrinking to near-zero when needed, compatible with container and Kubernetes environments. |
| Network Efficiency | 50% reduction in bandwidth (Parent-to-Parent streaming) | Implemented message combining for multiple metric updates, enabling higher compression ratios and reduced network overhead through larger network frames when streaming between Parent nodes. |
| Processing Performance | 20% reduction in CPU usage (Parent-to-Parent streaming) | Improved lock contention with advanced algorithms, enhancing fairness, responsiveness, and scalability specifically for Parents streaming to other Parents. DBEngine cache now delivers full capacity at scale. |
| Startup Performance | Significantly faster startup | Parallelized metadata loading based on available CPU cores, resulting in significantly reduced loading times. |
| Configuration Management | New profile system | Introduced auto-detected configuration profiles: - Parent: Optimized for data transfer between parents. - Child: Minimized resource footprint. - IoT: Configured for minimum resource usage. |
| Cloud Connectivity | Enhanced reliability | Reworked code to ensure stable Netdata Cloud connectivity under heavy load conditions on busy Netdata Parents. |
Enhanced Single Node Dashboard View
Introducing an improved single-node dashboard experience! You can now open a dedicated dashboard for any node directly from the Nodes tab (or other locations), giving you instant access to all critical data related to that node.
The dashboard consolidates essential information into intuitive tabbed views, including:
- Metrics
- Top
- Logs
- Alerts
- Anomalies
- Events
With automatic data filtering specific to the selected node, you can navigate seamlessly between tabs to quickly access troubleshooting insights. When you're done, the entire dashboard can be closed effortlessly with a single click.
This streamlined experience makes monitoring and managing individual nodes easier and faster than ever before.
Personalized Space Navigation
Customizable Space Navigation
You can now personalize the order and appearance of your space icons in the left panel:
- Reorder Spaces: Simply drag and drop space icons to organize them in the order that works best for you.
- Customize Colors: Use the color picker to assign unique colors to your space icons, making them easily distinguishable.
- Save Preferences: Your customizations are saved automatically, ensuring a consistent experience every time you access your dashboard.
If you have multiple spaces, you can now find and access the spaces you are looking for much faster and more intuitively than before.
Acknowledgments
- @enoch85 for adding instructions for setting up email notifications for Docker Compose.
Contributions
Collectors
Improvements
- Add collector for optical transceiver modules (go.d/ethtool) (#19426, #19428,#19429, #19430, #19434 @ilyam8)
- Add support for Pod exclusion using
netdata.cloud/ignoreannotation (go.d/k8s_state) (#19342, @ilyam8) - Add container filtering via
netdata.cloud/ignorelabel (go.d/docker) (#19341, @ilyam8) - Add a configuration option to filter containers (go.d/docker) (#19337, #19339 @ilyam8)
- Add collector for YugabyteDB (go.d/yugabytedb) (#19325, @ilyam8)
- Add container filtering via
netdata.cloud/*labels (cgroups.plugin) (#19315, #19316, #19318 @ktsaou @ilyam8) - Add collector for NATS (go.d/nats) (#19252, #19253, #19262, #19264, #19266, #19280, #19282, #19284, #19285, #19303, #19309,#19311, @ilyam8)
- Port sensors collector from Go to C (debugfs/sensors) (#19251, #19294 [@ktsaou](https:...
