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!

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:

• Include Go version in build info (#21473, @ilyam8)
• Update go toolchain to v1.25.5 (#21459, @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!

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_version check 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_entries as 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!

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!

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!

Table of Contents

• Summary
• Highlights
• Acknowledgments
• Contributions
  • Collectors
  • Packaging/Installation
  • Documentation
  • Other Notable Changes
• Deprecation notice
• Support options

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.

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:

1. 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.
2. Correlate: Leverage Netdata AI to automatically find other metrics in your system that correlate with the behavior of the chart you are viewing.
3. Drill Down: Explore related metrics and child contexts using Weights Analysis to understand which specific dimensions are driving the spike.
4. 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.

What You Get

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

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_service from 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/data to correctly report update_every after 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!

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-json at 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!

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!

Table of Contents

• Summary
• Highlights
• Acknowledgments
• Contributions
  • Collectors
  • Packaging/Installation
  • Documentation
  • Other Notable Changes
• Deprecation notice
• Support options

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.

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.

What’s Inside

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

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

Default Network Interface IP Detection

Netdata now automatically detects the IP address of the netwo...