Releases: netdata/netdata
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!
v2.7.0
Table of Contents
Release Summary
Netdata v2.7.0 introduces powerful new capabilities and continues our commitment to stability with significant improvements to system robustness. This release contains numerous under-the-hood improvements aimed at making Netdata more reliable in production.
| Highlight | Summary |
|---|---|
| Netdata AI | Automated troubleshooting, on-demand analysis, scheduled infrastructure reports and more. |
| Chart Annotations | Create shared annotations on any chart to mark deployments, incidents, or other key events for your team. |
| Quick Data Export | Export data from any chart, table, or log view to various formats (CSV, PNG, PDF) for offline analysis. |
| OpenTelemetry (Alpha) | New otel.plugin ingests metrics via OTLP gRPC and maps them into Netdata charts. Experimental and evolving. |
| SNMP Profiles Stable | Profiles are now stable and the default method, with improved metadata (~15k entries) and better coverage. |
| Default IP Detection | Nodes are now displayed as NodeName (IP), making it easier to identify and filter systems by IP. |
| Stability Improvements | Contains fixes to eliminate potential crashes and resolve memory issues. |
Release Highlights
Introducing Netdata AI: Your Co-SRE for Automated Analysis
Netdata AI is a step-change in how teams work with infrastructure observability data. Above and beyond visualizing all your metrics in beautiful real time charts, Netdata AI synthesizes your per-second metrics into clear explanations, timelines, and actionable reports. It's designed to automate the heavy lifting of troubleshooting and analysis for you.
Key Capabilities:
- AI Insights: Generate on-demand reports for common SRE tasks like performance optimization, capacity planning, and weekly infrastructure summaries.
- Automated Investigations: Run open-ended investigations and explorations or just ask questions in plain English (e.g., "Why are my Kubernetes pods in us-east-1 crashing?") and get a detailed, evidence-backed report in minutes.
- Alert Troubleshooting: Get a root-cause analysis for any active alert with a single click.
- Scheduled Reports: Automate your reporting by scheduling any investigation, like a weekly health check or a monthly performance analysis, to run automatically.
- Share & Export: Download any AI report as a professional PDF for offline sharing, or share it directly with teammates via email from within the Netdata Cloud UI.
How to use it:
Visit the "AI Insights" tab, or interact with Ask AI and/or "Troubleshoot" buttons throughout Netdata Cloud. All users on Trial, Business and Homelab plans have access to 10 free AI sessions. Further sessions can be purchased in-app. If you are on the community plan and would like to try out Netdata AI, please sign up to the waitlist.
Chart Annotations: Mark and Share Key Events
You can now create annotations directly on any Netdata chart to mark and share important context with your team.
How to use it:
Simply click on any chart at the desired timestamp to add a note and a color-coded marker. This marker will be visible to your entire team, providing a shared timeline of events.
Common Use Cases:
- 📌 Mark Deployments: Pinpoint the exact time a new software version was released.
- 🔥 Log Incidents: Mark the start and end times of an incident for easier post-mortems.
- ⚙️ Track Changes: Note when a critical configuration change was applied.
- 💬 Add Context: Leave notes for teammates to explain a specific anomaly or trend.
Quick Data Export
We've added comprehensive data export capabilities directly within the Netdata Cloud Dashboards, allowing you to take your data offline for custom reporting, further analysis, or sharing.
What you can export:
- From Charts: Download the data visualized in any chart as a CSV, raw data file, PNG image, or PDF document.
- From Tables & Logs: Export the data from any table—including in the Logs, Events, and Alerts tabs—as a CSV file.
How to use it:
Look for the download icon on any chart or table to access the new export options.
OpenTelemetry Metrics Ingestion (Alpha)
The new otel.plugin enables Netdata to ingest metrics from the OpenTelemetry ecosystem. It lets you bring in metrics from services and apps already instrumented with OpenTelemetry, unifying them with the high-resolution system metrics that Netdata provides. No extra exporters required. This is an early-stage feature, so configuration and custom mappings are still experimental and may change.
Important
As an alpha release, expect rapid improvements and possible configuration changes in future versions.
What’s Inside
| Capability | Details |
|---|---|
| OTLP gRPC Endpoint | Listens on port 4317 for incoming metrics |
| Flexible Sources | Works with an OpenTelemetry Collector or directly from apps |
| Automatic Mapping | Transforms OTel metrics into Netdata charts with minimal setup |
| Alpha Status | Early stage, limited docs, experimental configuration, subject to change |
SNMP Monitoring with Device Profiles: Now Stable
Introduced as alpha in v2.6.0, SNMP profile-based collection has now matured into the default and recommended method for SNMP monitoring in Netdata. The old custom OID method is deprecated and disabled by default.
What’s New
| Improvement | Details |
|---|---|
| Better Device Metadata | Accurate vendor, model, and category detection with new metadata files, including ~15,000 entries across major vendors (Cisco, Juniper, Huawei, D-Link, Aruba, Arista, Allied, and more) |
| Improved Profiles | Enhanced and more complete SNMP profiles for a smoother experience |
| Bug Fixes | All known issues resolved |
What You Get
- Reliable device identification (Router, Switch, Firewall, etc.) without manual setup
- Automatic vendor and model recognition across a wide range of devices
- A reliable and stable monitoring method that is now the default
Tip
We’re continuing to expand coverage based on user feedback. Missing metrics for your devices? Let us know!
Default Network Interface IP Detection
Netdata now automatically detects the IP address of the netwo...
Contributors
Assets 16
v2.6.3
Netdata v2.6.3 is a patch release to address issues discovered since v2.6.2.
This patch release provides the following bug fixes and updates:
- Added build-time check to reject known bad compiler flags (#20851, @Ferroin)
- Fixed saving of virtual host labels and removed incorrect live flag on agent restart (#20841, #20845, @stelfrag)
- Added various improvements to SNMP profiles and go.d/snmp collector (#20819, #20827, #20828, #20830, #20831, #20835, #20837, #20839, #20844, #20861, #20863, @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.6.2
Netdata v2.6.2 is a patch release to address issues discovered since v2.6.1.
This patch release provides the following bug fixes and updates:
- Fixed packet ID clearing when processing PUBACK messages (#20808, @stelfrag)
- Added detailed pulse metrics for ACLK telemetry including latency and queue wait time statistics (#20802, @ktsaou)
- Made virtual nodes inherit the version from their parent agent (#20777, @stelfrag)
- Improved ACLK with periodic cleanup of pending PUBACKs, fixed lock ordering to prevent deadlocks, and added pending PUBACK statistics (#20775, #20800, @stelfrag)
- Added publish latency metrics to
netdatacli aclk-statecommand and/api/v1/aclkendpoint (#20769, @stelfrag) - Fixed packet timeout handling corruption on 32-bit systems (#20766, @stelfrag)
- Added default network interface IP detection to system-info (#20764, @ilyam8)
- Removed
patternPropertiesfrom go.d config_schema.json files (#20763, @ilyam8) - Added security validation for custom binary paths in go.d.plugin (#20761, #20798, #20801, @ilyam8)
- Improved disk usage measurement accuracy in Windows plugin (#20752, @thiagoftsm)
- Added proxy information to ACLK connection logs and
netdatacli aclk-stateoutput (#20747, @stelfrag) - Added various improvements to SNMP profiles and go.d/snmp collector (#20745, #20750, #20751, #20754, #20755, #20756, #20757, #20762, #20768, #20770, #20784, #20786, #20787, #20803, #20805, #20813, #20814, @ilyam8)
- Updated OpenSSL to 3.4.2 and curl to 8.15.0 in static builds (#20734, @ilyam8)
- Added database checks to prevent statement finalization after databases have been closed (#20731, @stelfrag)
- Added Oracle Linux 10 and Debian 13 support to CI and package builds (#20684, #20776, @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.6.1
Netdata v2.6.1 is a patch release to address issues discovered since v2.6.0.
This patch release provides the following bug fixes and updates:
- Fixed double-release protection by resetting chart variables to null after release (#20727, @stelfrag)
- Fixed initialization of thread synchronization primitives by using dynamic allocation instead of static initialization (#20722, @stelfrag)
- Fixed worker thread completion signaling by moving it from callback to the worker thread itself (#20719, @stelfrag)
- Added SNMP profile device metadata to virtual node labels for better device identification and organization (#20718, @ilyam8)
- Fixed build reproducibility by excluding timestamps from gzip metadata when compressing build information (#20714, @Antiz96)
- Fixed ACLK MQTT packet handling by adding timeout detection for missing acknowledgments and increasing buffer size for parent agents (#20711, @stelfrag)
- Fixed SNMP device profiles to convert non-UCUM units to proper UCUM format (#20710, @Ancairon)
- Fixed NVMe collector to query controller-level SMART metrics instead of namespace-level to improve compatibility and reduce redundant queries (#20704, @ilyam8)
- Updated eBPF CO-RE library to version 1.6.0 (#20696, @thiagoftsm)
- Fixed SSL certificate detection on Rocky Linux and for static builds by adding proper certificate paths and symlink creation (#20695, @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.6.0
Table of Contents
Release Summary
This release brings AI-powered monitoring intelligence and expanded platform support to all Netdata users.
| Feature | What's New |
|---|---|
| AI Integration | • MCP server support enables AI assistants to query your infrastructure • Natural language questions in AI Insights ("What went wrong at 3 PM?") |
| Enterprise Integration | • Full SCIM group provisioning for Okta • Automatic space/room access based on Okta groups |
| Network Monitoring | • SNMP profile-based collection with 100+ device profiles (alpha) • Auto-detection for Cisco, Palo Alto, F5, and more |
| Platform Expansion | • Native packages for RHEL 10, AlmaLinux 10, Rocky Linux 10 • systemd journal support for static builds via Rust implementation |
Release Highlights
Model Context Protocol (MCP) Server Integration
Every Netdata Agent and Parent now functions as an MCP server, enabling AI assistants like Claude Desktop to query and analyze your infrastructure monitoring data through a built-in WebSocket interface.
What MCP Enables
AI assistants gain read-only access to your monitoring data:
- Infrastructure Discovery: Hardware specs, OS details, and streaming topology
- Metric Intelligence: Full-text search across all contexts, instances, dimensions, and labels
- System Insights: Execute functions for processes, network connections, systemd journals, and Windows events
- Alert Analysis: View real-time alerts and complete alert history
- Advanced Analytics: Complex metric queries with ML-powered anomaly detection
- Root Cause Analysis: Correlate metrics and anomaly scores to identify issues
Security First
- Sensitive functions (logs, process monitoring) require temporary API keys
- Existing Netdata permissions control all data access
- WebSocket connections need explicit configuration in AI clients
Scalable Visibility
AI assistant visibility scales with your connection point:
| Connection Point | Visibility Scope |
|---|---|
| Netdata Child/Standalone | Single node only |
| Netdata Parent | Parent + all connected children |
| Netdata Cloud | Full infrastructure (coming soon) |
AI Insights: Enhanced with Natural Language Investigation
AI Insights now understands your questions. Simply ask "What went wrong yesterday at 3 PM?" and get a comprehensive report targeting your specific concern—no more manual metric correlation or dashboard hunting during incidents.
Available Reports
| Report Type | Analysis Period | Answers Questions Like |
|---|---|---|
| Infrastructure Summary | 24 hours - 1 month | "How healthy is my infrastructure?" |
| Capacity Planning | 3 months - 2 years | "When will I run out of resources?" |
| Performance Optimization | 24 hours - 1 quarter | "Where are my bottlenecks?" |
| Anomaly Analysis | 6 hours - 7 days | "What caused the outage?" |
| Investigation (NEW) | Custom timeframe | "Why did latency spike at 3 PM?" |
| Alert Troubleshooting | Real-time | "How do I fix this alert?" (Preview) |
What's New
- Natural Language Queries: Ask questions in plain English about any timeframe or issue
- Targeted Analysis: Get reports focused on your specific problem, not generic overviews
- Alert Resolution Guidance: Coming soon—automated investigation of active alerts with fix recommendations
Privacy and Limits
- Reports are generated on-demand and immediately disposed
- Your infrastructure data is never used for AI training
- All reports share the monthly limit of 10 reports
Note
Alert Troubleshooting is currently in preview and will be gradually rolled out to all users.
Okta Integration: Full SCIM Group Provisioning Support
The Okta integration now supports complete SCIM group provisioning, enabling automatic synchronization of both users and groups between Okta and Netdata Cloud.
What's New
Previously limited to user provisioning, the integration now includes:
| Capability | Before | Now |
|---|---|---|
| User Provisioning | ✅ Create, update, deactivate users | ✅ Create, update, deactivate users |
| Group Sync | ❌ Manual group management | ✅ Automatic group synchronization |
| Space/Room Access | ❌ Manual assignment | ✅ Auto-assignment based on Okta groups |
Automated Access Management
When you add or remove users from groups in Okta, these changes instantly reflect in Netdata Cloud. This enables powerful automation scenarios:
- Assign users to specific Netdata spaces based on their Okta department groups
- Grant room access automatically based on team membership
- Revoke access immediately when users leave groups
Learn how to configure SCIM group provisioning in our documentation or explore the Netdata integration in Okta's marketplace.
Automated SNMP Monitoring with Device Profiles
Netdata v2.6.0 adds SNMP profile-based collection (alpha), transforming complex SNMP monitoring into a plug-and-play experience. The profile system makes enterprise network monitoring accessible to everyone, from home labs to data centers, with the simplicity Netdata is known for.
Getting started is simple:
- Existing users: Profiles are automatically enabled and your devices will be detected and monitored with no additional configuration
- New users: Just configure SNMP credentials, and Netdata handles the rest
Important
As an alpha release, expect rapid improvements and possible profile format changes in future versions.
What's New
| Before | Now with Profiles |
|---|---|
| Manual OID configuration | Auto-detection with 100+ device profiles |
| Limited to IF-MIB metrics | Full device metrics: CPU, memory, temperature, status |
| Complex setup per device | Drop-in YAML profiles |
| No vendor intelligence | Vendor-specific metrics and transformations |
| Fixed monitoring only | Support for custom profiles for specialized devices |
Extensive Device Coverage
Netdata ships with profiles for major network vendors, adapted from Datadog’s battle-tested definitions:
| Category | Vendors Included |
|---|---|
| Switches & Routers | Cisco (Catalyst, Nexus, ASR, ISR), Arista, Juniper, HP/HPE, Dell, Extreme |
| Firewalls | Palo Alto, Fortinet FortiGate, Cisco ASA, Checkpoint, SonicWall |
| Wireless | Aruba, Cisco WLC, Ubiquiti, Alcatel-Lucent |
| Load Balancers | F5 BIG-IP, Citrix NetScaler, A10 Thunder |
| Infrastructure | APC UPS/PDU, Dell servers, standard MIBs (BGP, OSPF, TCP/UDP) |
Tip
This is just the beginning. We're actively expanding coverage based on user feedback. Missing metrics for your devices? Let us know!
Native Package Support for RHEL 10 and Derivatives
Netdata now provides native packages for RHEL 10, AlmaLinux 10, and Rocky Linux 10.
These packages ensure seamless integration with corporate deployment tools, automated updates, and compliance requirements typical in enterprise environments. Whether you're running RHEL 10 in production or using AlmaLinux or Rocky Linux as alternatives, you get the same reliable, optimized Netdata experience.
Rust-Based systemd-journal Plugin for Static Builds
Static build users can now access sy...
Contributors
Assets 16
v2.5.4
Netdata v2.5.4 is a patch release to address issues discovered since v2.5.3.
This patch release provides the following bug fixes and updates:
- Improved label sanitization in Go plugins by removing null bytes from values (commit, @ilyam8)
- Improved Go plugin startup performance by loading SNMP profiles only when used instead of all at startup (commit, @ilyam8)
- Added
-NoProfileparameter to Windows installer PowerShell execution for cleaner environment setup (#20550, @thiagoftsm) - Optimized memory usage by switching label structures to use the ARAL allocator and reducing memory footprint (#20502, @stelfrag)
- Fixed CPU architecture matching for Go plugin builds in 32-bit static builds (#20502, @Ferroin)
- Fixed Redis collector to properly maintain TLS configuration for
redissconnections (#20478, @ilyam8) - Fixed Go weblog collector to exclude HTTP 429 status codes from 4xx error category (#20443, @Slind14)
- Fixed registry save operation by correcting integer overflow issues and adding exponential backoff for failed save attempts (#20437, @ktsaou)
- Improved agent shutdown responsiveness by reducing streaming connection timeout from 1000ms to 250ms (#20434, @stelfrag)
- Fixed database statement handling with improved thread cleanup and validation before finalization (#20433, @stelfrag)
- Fixed memory corruption issue in query progress updates by preventing access to freed web client structures (#20431, @ktsaou)
- Added vendored Protobuf and Abseil libraries to static builds with necessary patches for cross-platform compatibility (#17774, @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.5.3
Netdata v2.5.3 is a patch release to address issues discovered since v2.5.2.
This patch release provides the following bug fixes and updates:
- Fixed context update handling by adjusting conditions for hub queue management (#20416, @stelfrag)
- Added ability to debug individual jobs in go.d.plugin instead of all jobs within a module (#20394, @ilyam8)
- Added debug logging for HTTP response validation in go.d.plugin HTTP check collector (#20392, @ilyam8)
- Fixed duplicate name handling in go.d.plugin dynamic configuration userconfig action (#20346, @ilyam8)
- Fixed Oracle database collector to correctly calculate tablespace usage percentages and prevent negative values (#20373, #20378, @ilyam8)
- Fixed database engine performance by optimizing file rotation and indexing operations with better job scheduling and concurrency handling (#20354, @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!