Skip to main content

Release 1.41.0: Netdata Agents and Parents now have a new UI!

· 13 min read
Netdata Team

Netdata Agents and Parents now have a new UI!

image

Checkout the release meetup video or read on to learn more about the new UI and other features in this release.

Steady to our schedule, this is another great Netdata release!

Netdata Growth ​

  • 64 k GitHub Stars ⭐
  • 1.7 M monitored nodes
  • 570+ M docker hub pulls

Give Netdata a ⭐ too, on Github!

❤️ Thank you for your love! 🚀 You rock!

Release Highlights ​

New Agent Dashboard ​

Netdata Agents and Parents now have a new UI!

New CHARTS 🟢 New SUMMARIES 🟢 MACHINE-LEARNING FIRST 🟢 INFRASTRUCTURE LEVEL DASHBOARDS 🟢 FILTER, SLICE, and DICE any dataset 🟢 ANOMALY ADVISOR 🟢 METRICS CORRELATIONS 🟢 NETDATA FUNCTIONS 🟢 EVENTS FEED 🟢 HEATMAPS 🟢

Netdata Agent

In the last few months, we have ported and open-sourced all Netdata Cloud APIs to the Netdata Agent, allowing Netdata Parents to drive the same multi-node / infrastructure level dashboards Netdata Cloud provides!

So, as of today, Netdata Agents and Parents present the same UI, exactly the same dashboard, charts and features with Netdata Cloud!

Single Node Dashboard Changes​

Apart from the entirely new look, single-node dashboards now group similar charts together. So, all disk drives, network interfaces, cgroups (containers and VMs), are now a single set of charts.

This allows Netdata to aggregate a vast amount of datasets in a chart, like the following, where almost 20k containers are now manageable:

image

To make it easier for you to navigate, filter, slice, and dice the data, the menus above each chart give you easy access to all the data of the chart:

Netdata Agent 2

Multi Node Dashboards​

When Netdata Agents are configured as Parents (multiple other agents stream metrics to them), they now present multi-node and multi-instance charts. At the top right corner of the dashboard, there is the global nodes filter, from which you can slice the entire dashboard for one or a few of your nodes.

image

Want to know more?​

Get a firsthand walkthrough with Costa Tsaousis, Netdata's Founder, on the rationale for this change and the path Netdata is taking by checking the video from Netdata Office Hours on YouTube.

The old dashboards are still accessible​

You can still access all versions of the dashboards, as follows:

  • http://your.server:19999/ The default dashboard is now a live version of the new UI. The dashboard static files are served by Cloudflare and are automatically updated when we release a new version of the UI, so that your Netdata agent is always up to date.

  • http://your.server:19999/v2/ A local copy of the latest dashboard, as it was at the time the agent was released. This is distributed with Netdata under the Netdata Cloud UI License v1.0. The local copy is automatically used if for any reason the web browser cannot download the live version of it.

  • http://your.server:19999/v1/ The previous single-node version of the Netdata Agent dashboard.

  • http://your.server:19999/v0/ The now ancient, original version of the Netdata Agent dashboard.

Netdata Assistant ​

Netdata Assistant: Your AI-Powered Troubleshooting Sidekick

The Netdata Assistant is an AI-powered tool that uses large language models and our community's knowledge to guide you during troubleshooting and help you get to the root cause sooner.

The goal of the Netdata Assistant is straightforward: to make your troubleshooting process easier. It's here to save you from the hassle of sifting through tons of information so you can focus on solving the problem at hand.

It will give you the lowdown on the alert, why it's happening, and why you should care. It'll also guide you on how to troubleshoot it and even offer some handy web links for more info if you're interested.

image

Read more about it on the Netdata blog here.

New FreeIPMI collector for monitoring enterprise hardware ​

Netdata got a new FreeIPMI collector. The new collector is able to collect IPMI sensors at a much better data collection rate, and it is more reliable and robust compared to the previous one.

We have also categorized all sensors based on the component they monitor:

image

And provided as labels the exact sensor name each metric refers to:

image

Netdata Detects FDs Leaking ​

"FD" stands for "file descriptor". A file descriptor is an integer that the operating system assigns to an open file to track it. This includes regular data files, directories, network sockets, pipes, and other types of I/O streams.

In Linux, everything is treated as a file, which includes hardware devices, directories, and sockets. Each open file is assigned a file descriptor. When a file is closed, its file descriptor is freed up for reuse. However, if an application doesn't close a file when it's done with it, that's called a "file descriptor leak".

File descriptor leaks can cause several problems:

  1. Resource exhaustion: Each process has a limit to the number of file descriptors it can open. If a process continually leaks file descriptors without closing them, it will eventually hit this limit and won't be able to open any more files, which often causes the process to crash.
  2. Unexpected behavior: Open file descriptors hold resources, like network sockets, that might be expected to be available for other uses. If these resources are tied up due to a leak, it can cause unexpected behavior.
  3. Security issues: File descriptors can sometimes be used to gain unauthorized access to data if they're not properly managed.

apps.plugins is now able to track the usage of FDs against the limits set for each application. We have added an fds category in the Applications section of the dashboard. The first chart shows the percentage of FDs used by each application against its limits:

image

Acknowledgements ​

We would like to thank our dedicated, talented contributors that make up this amazing community. The time and expertise that you volunteer are essential to our success. We thank you and look forward to continuing to grow together to build a remarkable product.

  • @k0ste for improving Prometheus exporting doc.
  • @carlocab for replacing `info` macro with a less generic name.
  • @MYanello for updating the pfSense package installation instructions.

Contributions ​

Collectors ​

Improvements​

  • Improve of fds monitoring (apps.plugin) (#15437, @ktsaou)
  • Add application groups file descriptor limit monitoring (apps.plugin) (#15417, @ktsaou)
  • Re-create sdr cache on start (freeipmi.plugin) (#15361, @ktsaou)
  • Add sensor state chart, create a per-sensor chart instead of a per-sensor dimension (freeipmi.plugin) (#15327, @ktsaou)
  • Expose CmdLine in apps function (apps.plugin) (#15275, @ilyam8)
  • Remove pod_uid and container_id labels in k8s (cgroups.plugin) (#15216, @ilyam8)
  • Add cluster mode (go.d/elasticsearch) (#1227, @ilyam8)
  • Add 'fallback_type' config option to match Untyped (go.d/prometheus) (#1225, @ilyam8)

Bug fixes​

  • Fix sensor state updates (freeipmi.plugin) (#15360, @ilyam8)
  • Fix tc.plugin charts labels (tc.plugin) (#15262, @ilyam8)
  • Fix collecting hostgroup from stats_mysql_connection_pool (go.d/proxysql) (#1226, @ilyam8)

Other​

Documentation ​

Packaging / Installation ​

Health ​

Exporting ​

  • Hide not available for viewers charts when exporting in the shell format (#15309, @ilyam8)
  • Fix slow exporting in Prometheus format (#15276, @ilyam8)

Other Notable Changes ​

Improvements​

  • Enrichment of /api/v2, buildinfo improvements and code cleanup (#15294, @ktsaou)

Bug fixes​

Code organization​

Deprecation notice ​

There is not an obvious list of items that will be deprecated in the upcoming release (v1.42.0). Feel free to check and elaborate on the upcoming backlog

Deprecated in this release ​

In accordance with our previous deprecation notice, the following items in this release:

ComponentTypeWill be replaced by
python.d/nvidia_smicollectorgo.d/nvidia_smi
family attributealert configuration and Health APIchart labels attribute (more details on netdata#15030)

Netdata Release Meetup ​

Join the Netdata team on the 21st of July at 17:00 UTC for the Netdata Release Meetup.

Together we’ll cover:

  • Release Highlights.
  • Acknowledgements.
  • Q&A with the community.

RSVP now - we look forward to meeting you.

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 1400 engineers are already using it!