Netdata logo

Netdata

Real-time infrastructure and application monitoring platform

Alternative to: Prometheus, Grafana, Nagios, Zabbix, Datadog, New Relic, Sensu, Dynatrace

Netdata screenshot

About Versions (102)

v1.47.0

2024-08-22

Table of Contents

Netdata Growth

  • 1.5 million downloads per day
  • 70.1k GitHub stars!
  • 642.7M Docker Hub pulls!

Netdata is being downloaded more than 1.5 million times per day, as reported by Cloudflare, which distributes our binary packages, and Docker Hub, which distributes our docker containers!

Thanks to your love ❤️, Netdata is leading the observability category in the CNCF landscape, having significantly more stars than Elasticsearch, Grafana, Prometheus and all other observability solutions.

We are committed to provide the most advanced and innovative AI-powered, cloud-native and on-premises observability solution, to help us have higher-fidelity AI-insights, while being easier, faster, simpler, and significantly more affordable!

You like Netdata? Give Netdata a ⭐ too, on GitHub!

Release Summary

This marks the final release of Netdata Agent v1.x, with v1.47 being the last in this series. Right after, we will start merging code for the upcoming version of the Agent: v2.0. This means that there will not be any nightlies starting with 1.47.0-nightly-, but instead we will have 1.99.0-nightly-. See below for more on what is to come in Netdata Agent 2.0.

Release Highlights

The following key improvements are released today:

SNMP Plugin Enhancements

The SNMP plugin now features automatic discovery of all network interfaces on SNMP devices. After configuring the SNMP endpoints, the plugin collects:

  • Traffic data per interface.
  • Packet data (unicast, multicast, broadcast) per interface.
  • Error metrics per interface.
  • Discards and status (administrative and operational) per interface.
  • Device uptime.

The plugin supports all SNMP versions (v1, v2, v3).

Migration of Python Plugins to Go

Eighteen data collection modules have been migrated from Python to Go, bringing several benefits:

  • Auto-discovery of running processes via local-listeners.
  • Dynamic configuration support via the dashboard (dyncfg).
  • Instance labeling for enhanced data slicing and dicing on the dashboard.

The goal is to migrate all data collection plugins to Go eventually.

Introduction of Identity Management Integrations with SCIM

In this release we have introduced Identity Management support for enterprise users who want to manage user access to Netdata with their organisation IDM. This now allows users to integrate their SSO and IDM solutions with Netdata. Go through our documentation for more details.

SSO and IDM with Netdata

Enhancement of Reachability Notifications

The reachability notifications on Netdata Cloud have been enhanced in deployments that have Netdata parents (streaming enabled) as local centralisation points.

  • The notifications are grouped / coalesced through the Netdata Parents
  • If the Netdata Parent (last one in the cluster) becomes unreachable, a single unreachable notification is sent with details of all related nodes that are also unreachable as a result
  • If individual nodes become unreachable, the associated Netdata parent is referenced to help users check network connectivity issues within their infrastructure.

MS Teams Notification Integration using MS Workflows

Microsoft recently announced the deprecation of their legacy MS Connectors and has replaced it with the MS Workflows. This has forced us to modify our MS Teams notification integration. From immediate effect, old MS Teams integration will stop working and will need to be reconfigured following the documentation mentioned here.

Automatic Removal of Stale Nodes

For environments with high node turnover, the netdatacli tool now supports the bulk removal of stale nodes from a Netdata parent without requiring a restart. This removal process also purges stale nodes from the Netdata Agent dashboard and Netdata Cloud.

IPv6-Only Environment Support

Netdata now fully supports communication in IPv6-only environments. A forthcoming update to Netdata Cloud will enable IPv6-only agents to connect seamlessly.

Stale Alerts Fix

A new protocol for communicating alert transitions to Netdata Cloud has been implemented, resolving issues where alerts would remain in an invalid state.

Acknowledgments

  • @yoursweetginger for updating “Disable the local dashboard” section with Docker-specific instructions.
  • @Steve8291 for fixing logs section of the config readme.
  • @Hufschmidt for removing hard-coded url from python.d/puppet.

Contributions

Collectors

Rewritten
Improvements
  • Add virtual device health state collection (go.d/zfspool) (#18383, @ilyam8)
  • Improve parser initialization logic (go.d/squidlog) (#18368, @ilyam8)
  • Add i2pd to apps_groups.conf (#18335, @ilyam8)
  • Enable by default (go.d/nvidia) (#18315, @ilyam8)
  • Add loop mode for continuous GPU performance monitoring (go.d/nvidia) (#18313, @ilyam8)
  • Automatically adjusting max repetitions (go.d/snmp) (#18274, @ilyam8)
  • Add beanstalkd to apps_groups.conf (#18267, @ilyam8)
  • Add “not_revoked” dimension for improved certificate status visualization (go.d/x509check) (#18261, @ilyam8)
  • Add BBU capacity degradation percentage metric (go.d/megacli) (#18211, @ilyam8)
  • Use scan-open when “no_check_power_mode” is “never” (#18146, @ilyam8)
  • Optimize startup behavior by performing a single scan when interval is set to 0 (go.d/smartctl) (#18144, @ilyam8)
  • Add “extra_devices” option for manual device configuration (go.d/smartctl) (#18140, @ilyam8)
  • Add SCSI read/write/verify error rate metrics (go.d/smartctl) (#18119, @ilyam8)
  • Add port service names to network viewer (#18107, @ktsaou)
  • Add Docker environments support (go.d/fail2ban) (#18081, @ilyam8)
  • Improve security by masking sensitive configuration fields in collector config schemas (#18068, @ilyam8)
  • Update exclude paths/filesystems (diskspace.plugin) (#18039, @ilyam8)
  • Skip Jobs and CronJobs Pods (go.d/k8state) (#18028, @ilyam8)
  • Add interface filtering options (name and type) (go.d/snmp) (#18023, @ilyam8)
  • Add network interface statistics collection (go.d/snmp) (#18014, @ilyam8)
  • Improve cgroups version detection reliability (cgroups.plugin) (#17973, @ilyam8)
Bug fixes
  • Fix parsing of DHCP ranges with interface prefixes (go.d/dnsmasq_dhcp) (#18394, @ilyam8)
  • Fix compatibility with Dnsmasq v2.90+ by querying metrics individually (go.d/dnsmasq) (#18376, @ilyam8)
  • Fix file descriptors leak and improve memory usage (ebpf.plugin) (#18232, @thiagoftsm)
  • Fix chrony collector by adding read/write timeout to prevent hangs (go.d/chrony) (#18215, @ilyam8)
  • Fix URL path overwrite issue (go.d.plugin) (#18132, @ilyam8)
  • Fix parser configuration documentation (go.d/weblog) (#18037, @ilyam8)
Other

Packaging/Installation

All changes

Documentation

All changes

Other Notable Changes

Improvements
  • Add ALL_NODES keyword and node hostname parameter to remove-stale-node command for flexible stale node removal, including the ability to remove all stale nodes at once (#18386, @stelfrag)
  • Detect on startup if the netdata-meta.db file is not a valid database file (#17924, @stelfrag)
  • Support IPV6 when establishing MQTT connection to the cloud (#18217, @stelfrag)
Other

Deprecation notice

Changed in this release: Rewritten/Changed collectors

Rewritten Collectors: we have rewritten a number of collectors from Python (python.d.plugin) to Go (go.d.plugin).

Deprecated Collector (Python)Replacement Collector (Go)
python.d/apgo.d/ap
python.d/beanstalkgo.d/beanstalk
python.d/dovecotgo.d/dovecot
python.d/eximgo.d/exim
python.d/gearmango.d/gearman
python.d/icecastgo.d/icecast
python.d/ipfsgo.d/ipfs
python.d/memcachedgo.d/memcached
python.d/monitgo.d/monit
python.d/nsdgo.d/nsd
python.d/postfixgo.d/postfix
python.d/puppetgo.d/puppet
python.d/rethinkdbgo.d/rethinkdb
python.d/riakkvgo.d/riakkv
python.d/squidgo.d/squid
python.d/tomcatgo.d/tomcat
python.d/torgo.d/tor
python.d/uwsgigo.d/uwsgi

Important Note: While most users won’t experience any disruption, there’s one key point to consider if you’re heavily relying on Netdata’s metrics, such as exporting data to an external Time-Series Database (TSDB) or creating custom alerts. Due to the rewrite, the names of some metrics in some collectors have been changed. You may need to update your configurations to reflect the new metric names to avoid disruptions in your workflows.

To view a complete list of all metrics collected by a specific collector, refer to its documentation.

Removed Collectors

Removed Collector (Python)Reason
python.d/changefinderUnnecessary due to built-in anomaly detection. Unmaintained and uses unmaintained third-party library.
python.d/exampleRedundant due to existing Python collectors.
python.d/retroshareStatistics no longer available in upstream project.

Upcoming changes for Netdata Agent v2.0

The upcoming version of the Netdata Agent, v2.0, is nearing completion (and should be available early September) and will begin merging into the nightly channel immediately after the release of v1.47. Users of our nightly release channel will start experiencing parts of Netdata v2.0 as they are integrated, reflected in the version numbers starting with 1.99.0-nightly-.

Microsoft Windows Support

Netdata v2.0 will extend full native support to Windows servers and desktops, matching the feature set currently available on Linux, FreeBSD, and macOS. Users on the nightlies release can begin using Windows nodes across all dashboards as a beta. However, once mark this as GA, access to Windows nodes will be restricted to customers with a Netdata paid plan.

Netdata UI v3

The new dashboard (Netdata UI v3) will introduce several enhancements, including:

  • A new table of contents for metrics.
  • Improved log analysis with advanced customization options.
  • Controlled access to Netdata agents.
  • Unified features for both Netdata Agent and Netdata Cloud dashboards.

The dashboard will be split into two components:

  1. Open-source splash screen: Distributed with the Netdata agent, it provides information about the running agent, helps users log in to Netdata Cloud, and allows them to claim the agent.
  2. Main dashboard: Available as a separate package for local installation or accessible via a CDN.

Netdata UI v3 will utilize the new Netdata API v3. Consequently, all prior versions of dashboards (v0, v1, v2) will be removed, as well the the old APIs (v1, v2). Without logging into Netdata Cloud, the new v3 UI will continue to be usable as a fallback, with reduced functionality, similar to v2 and aligned with our Community Plan.

Netdata Cloud as a License Manager and Single-Sign-On Provider

For environments isolated from the internet, Netdata v2.0 will allow Netdata Cloud to function as:

  • A license manager, either directly or through a Netdata Parent.
  • A Single-Sign-On (SSO) provider, controlling access to local agent dashboards.

When configured in this manner, observability data remains within the isolated environment, ensuring all access is authenticated and authorized.

Other notes

  • The main dashboard artifacts will be removed from the main Agent code repository. For native builds, we will publish them as a new dependency package. For other builds, through the kickstart script, we will download the required artifacts.
  • Going forward, the Agent will always be built with support for Netdata Cloud.

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:

  • Premium Support: Customers who wish to have a direct channel with Netdata and prioritised support with defined SLAs can reach out to us.
  • 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!