<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ansible on Netdata</title><link>https://www.netdata.cloud/tags/ansible/</link><description>Recent content in Ansible on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 07 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/ansible/index.xml" rel="self" type="application/rss+xml"/><item><title>Netdata &amp; Ansible example: ML demo room</title><link>https://www.netdata.cloud/blog/ml-demo-ansible-configuration-management/</link><pubDate>Fri, 07 Jul 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/ml-demo-ansible-configuration-management/</guid><description>&lt;p>We are always trying to lower the barrier to entry when it comes to monitoring and observability and one place we have consistently witnessed some pain from users is around adopting and approaching &lt;a href="https://www.atlassian.com/microservices/microservices-architecture/configuration-management">configuration management&lt;/a> tools and practices as your infrastructure grows and becomes more complex.&lt;/p>
&lt;p>To that end, we have begun recently publishing our own &lt;a href="https://github.com/netdata/community/tree/main/configuration-management/ansible-ml-demo">little example ansible project&lt;/a> used to maintain and manage the servers used in our public &lt;a href="https://app.netdata.cloud/spaces/netdata-demo/rooms/machine-learning/overview">Machine Learning Demo room&lt;/a>.&lt;/p></description></item></channel></rss>