News Item 1

14-02-2022

In version v1.32 of Netdata, we announced a remarkable new update that we are extremely proud of; Netdata Cloud now runs on the most reliable and stable backend that we’ve ever built. The architectural changes allow us to deliver new features, such as parent-child relationships and improved alert handling. 

Along with an overhauled backend, we also updated the Agent Cloud Link, which lets you connect nodes to the Netdata Cloud. ACLK-ng (new generation) is up to 4x faster than ACLK legacy. Since we introduced ACLK-ng back in v1.30, we deprecated the ACLK legacy in v1.33 of Netdata.

Switching from JSON to Protocol Buffers (protobuf)

We’re constantly looking for ways to make Netdata Cloud even faster and work as seamless as possible with the Netdata Agent. In the past, we’ve used JSON to transmit metadata between nodes. However, making the switch to protobuf allows us to leverage high speeds and reliability because of its message format and schemas. Another benefit: protobuf uses less bandwidth than its predecessor.

Migration to the new Netdata Cloud architecture

To give you the best experience of Netdata Cloud, we started migrating nodes running on the old architecture to the new one. Most users don’t have to take any action on their part. If you need to take action, you will see the following banner in Netdata Cloud.  

Get ready for the new architecture

Let’s look at what you need to do to ensure that your nodes are still reachable after 1st of March 2022. To determine what steps you need to take, you need to check what type of installation you have.

Starting with Netdata v1.33.0, you can use Netdata itself to determine the installation type by running: netdata -W buildinfo | grep 'Install type:'

If your node has an installation of Netdata prior to v1.33, you will need to look into your node’s configuration document.

In your terminal: 

  1. Use cd to navigate to the configuration directory. In most cases, this is /etc/netdata.
  2. Use ls -a to look for a file called .install-type
  3. Check the file contents with cat .install-type.

The value of INSTALL_TYPE indicates the type of installation.

If you don’t have an .install-type file, look for an .environment file instead. If you see an .environment file, you have a static or build install. If the file does not exist, you have a custom install.

Static build or Docker installation

If you use Netdata in Docker, or have installed Netdata as a static build, for example, by using the kickstart script:

•  Update your Netdata agents to the latest version
   📄 Update Netdata

*-build installation
Because the new architecture of Netdata Cloud relies on protobuf:

• Update your Netdata agents to the latest version
  📄 Update Netdata

• Install a C++ compiler

binpkg-* installation

Binpkg type of installations should not experience any difficulties with the new architecture. If you run into an error:

• File a bug on GitHub

Other installation methods

As per Netdata’s platform support policy, there are packages that are not maintained by us. If a community-maintained package isn’t compatible with the new architecture:

• File a bug with the appropriate package maintainer

We hope you are just as excited as we are for the switch to the new architecture. While you can already enjoy benefits like lightning speed and extreme reliability, we have created a solid foundation to make your troubleshooting experience even more fun. In our upcoming releases, you will get access to an enhanced alert management experience.

Get Netdata

Sign in free to Netdata Cloud, connect the Agent and go