<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rooms on Netdata</title><link>https://www.netdata.cloud/tags/rooms/</link><description>Recent content in Rooms on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 28 May 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/rooms/index.xml" rel="self" type="application/rss+xml"/><item><title>How to automate adding nodes to rooms in Netdata?</title><link>https://www.netdata.cloud/blog/how-can-netdata-agents-be-placed-in-different-rooms-in-an-automated-way/</link><pubDate>Tue, 28 May 2024 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/how-can-netdata-agents-be-placed-in-different-rooms-in-an-automated-way/</guid><description>&lt;p>How we organize nodes (and the Netdata agents that are running on those nodes) across different rooms should reflect our architectural decision because the room is a logical container with its own user members and notification rules. So if we are monitoring large infrastructure we should be consistent with these rules and one way to achieve this is to choose automation. &lt;a href="https://registry.terraform.io/providers/netdata/netdata/latest">Netdata Cloud Terraform Provider&lt;/a> lets you automate this by provisioning all the cloud resources and giving you the credentials to spin up the Netdata Agents. In this article, we will concentrate on how in practice we can organize and assign nodes across different rooms in two scenarios, in each of them I&amp;rsquo;m using &lt;strong>non-production&lt;/strong> installation of the Netdata Agents:&lt;/p></description></item></channel></rss>