<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering on Netdata</title><link>https://www.netdata.cloud/tags/engineering/</link><description>Recent content in Engineering on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 13 Aug 2026 08:45:56 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Join Us</title><link>https://www.netdata.cloud/join-us/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/join-us/</guid><description>Build infrastructure observability at massive scale with Netdata. Remote-first culture, open source core, 76K+ GitHub stars. Own the full stack, ship code used by millions, work with world-class engineers.</description></item><item><title>Our Values and Promises</title><link>https://www.netdata.cloud/values/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/values/</guid><description>Discover the 12 principles that guide every decision at Netdata. From radical transparency to edge-native intelligence, learn how we invest engineering effort to eliminate complexity and align our success with your operational needs.</description></item><item><title>Upcoming Changes to Plugins in Native Packages</title><link>https://www.netdata.cloud/blog/split-plugin-packages/</link><pubDate>Wed, 15 Mar 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/split-plugin-packages/</guid><description>&lt;p>At Netdata, we’re committed to trying to make Netdata work as well as possible for our users. Sometimes though,
that means changing things in ways that aren’t exactly seamless. Such a change is coming soon for users of our
native DEB and RPM packages, and this blog post will explain what’s happening, why we’re doing it, and what
it means for our users.&lt;/p>
&lt;!-- truncate -->
&lt;h2 id="whats-changing">What’s changing?&lt;/h2>
&lt;p>Starting shortly after the v1.39.0 release of the Netdata Agent, we will be splitting most of our external
data collection plugins out to their own individual packages instead of bundling them all in the main &lt;code>netdata&lt;/code>
package. We already have this type of split for our CUPS and FreeIPMI plugins, and this new change will extend
that to also provide separate packages for the following plugins:&lt;/p></description></item><item><title>The Netdata Way of Troubleshooting</title><link>https://www.netdata.cloud/blog/the-netdata-way-of-troubleshooting/</link><pubDate>Mon, 04 Apr 2022 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/the-netdata-way-of-troubleshooting/</guid><description>&lt;p>Together with you, our fabulous community, Netdata is changing the way the world thinks of high fidelity monitoring - and we are gaining momentum.&lt;/p>
&lt;p>Our chief troublemaker and CEO, Costa Tsaousis,  is the pioneer and architect of this revolution that’s brewing in the monitoring and troubleshooting space.&lt;/p>
&lt;p>Watch him explain the &lt;strong>Netdata way of troubleshooting&lt;/strong>:&lt;/p>
&lt;iframe width="560" height="315" src="https://www.youtube.com/embed/ExjwwrgXvPg?si=IrsEp9PqbFFWiegM" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen>&lt;/iframe>
&lt;h2 id="why-did-the-world-need-a-new-infrastructure-monitoring-tool-0018">Why did the world need a new infrastructure monitoring tool? (00:18)&lt;/h2>
&lt;p>Every great hero needs an origin story. In this section, Costa explains the frustrating conditions in the infrastructure and monitoring space that lead to the conception, development, and subsequent success of the Netdata open-source Agent and Netdata Cloud.&lt;/p></description></item><item><title>All-new Netdata Cloud Charts 2.0</title><link>https://www.netdata.cloud/blog/all-new-netdata-cloud-charts-2-0/</link><pubDate>Tue, 30 Nov 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/all-new-netdata-cloud-charts-2-0/</guid><description>&lt;!--truncate-->
&lt;figure class="wp-block-image size-large">&lt;img src="../wp-archive/uploads/2022/03/Netdata-Charts-2.0-1200x704.png" alt="" class="wp-image-16212"/>&lt;/figure>
&lt;p>Netdata excels in collecting, storing, and organizing metrics in out-of-the-box dashboards for powerful troubleshooting. We are now doubling down on this by transforming data into even more effective visualizations, helping you make the most sense out of all your metrics for increased observability.&lt;/p>
&lt;p>The new Netdata Charts provide a ton of useful information and we invite you to further explore our new charts from a design and development perspective. As always, it’s our goal to be as open and transparent as possible with our users on all things Netdata, including the ins and outs of how Netdata is built, why we make certain design decisions (driven by you of course!), and where we are heading as we continue to grow.&lt;/p></description></item><item><title>How to extend the Geth collector</title><link>https://www.netdata.cloud/blog/how-to-extend-the-geth-collector/</link><pubDate>Mon, 13 Sep 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/how-to-extend-the-geth-collector/</guid><description>&lt;!--truncate-->
&lt;figure class="wp-block-image size-large">&lt;img src="../wp-archive/uploads/2022/03/Geth-collector-diagram-1-1200x796.png" alt="" class="wp-image-16282"/>&lt;/figure>
&lt;p>This is the the last of a 2-part blog post series regarding Netdata and Geth. If you missed the first, be sure to check it out &lt;a href="https://hackmd.io/J1x1WA-bR0a8gQeAmVdLFw" target="_blank" rel="noreferrer noopener">here&lt;/a>.&lt;/p>
&lt;p>Geth is short for Go-Ethereum and is the official implementation of the Ethereum Client in Go. Currently it’s one of the most widely used implementations and a core piece of infrastructure for the Ethereum ecosystem.&lt;/p>
&lt;p>With this proof of concept I wanted to showcase how easy it really is to gather data from any Prometheus endpoint and visualize them in Netdata. This has the added benefit of leveraging all the other features of Netdata, namely it’s per-second data collection, automatic deployment and configuration and superb system monitoring.&lt;/p></description></item><item><title>How to monitor the Geth node in under 5 minutes</title><link>https://www.netdata.cloud/blog/how-to-monitor-the-geth-node-in-under-5-minutes/</link><pubDate>Mon, 13 Sep 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/how-to-monitor-the-geth-node-in-under-5-minutes/</guid><description>&lt;!--truncate-->
&lt;figure class="wp-block-image size-large">&lt;img src="../wp-archive/uploads/2022/03/How-Geth-affect-the-CPU-charts-1200x629.png" alt="" class="wp-image-16229"/>&lt;/figure>
&lt;p>This piece is a blog post version of a workshop I gave at &lt;a href="https://ethcc.io/" target="_blank" rel="noreferrer noopener">EthCC&lt;/a> about monitoring an Ethereum Node using Netdata.&lt;/p>
&lt;p>&lt;strong>Disclaimer:&lt;/strong> Although we use Netdata, this guide is generic. We talk about metrics that can be surfaced by many other tools, such as Prometheus/Grafana or Datadog.&lt;/p>
&lt;p>The contents are as follows:&lt;/p>
&lt;ul>&lt;li class="">Introduction to Ethereum Nodes&lt;/li>&lt;li class="">What is Netdata&lt;/li>&lt;li class="">How to monitor a system that runs go-ethereum (Geth)&lt;/li>&lt;li class="">How to monitor go-ethereum (Geth)&lt;/li>&lt;/ul>
&lt;h2 id="ethereum-nodes">Ethereum Nodes&lt;/h2>
&lt;p>Running a node is no small feat, as it requires increasingly more and more resources to store the state of the blockchain and quickly process new transactions.&lt;/p></description></item><item><title>Root cause analysis using Metric Correlations</title><link>https://www.netdata.cloud/blog/root-cause-analysis-using-metric-correlations/</link><pubDate>Fri, 03 Sep 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/root-cause-analysis-using-metric-correlations/</guid><description>&lt;!--truncate-->
&lt;figure class="wp-block-image size-large">&lt;img src="../wp-archive/uploads/2022/03/Screen-Shot-2021-09-03-at-1.43.32-PM-1-1200x608.png" alt="" class="wp-image-16297"/>&lt;/figure>
&lt;p>As complexity of systems and applications continue to evolve and change, the number of metrics that need to be monitored grows in parallel. Whether you’re on a DevOps team, an SRE, or a developer building the code yourself, many of these components may be fragmented across your infrastructure, making it increasingly difficult to identify the root cause when experiencing downtime or abnormal behavior. To help solve this challenge, we built the &lt;a href="https://learn.netdata.cloud/docs/cloud/insights/metric-correlations">Metric Correlations&lt;/a> feature – an automated analysis tool that evaluates all your metrics to identify which have changed the most within a given period of interest.&lt;/p></description></item><item><title>How To Monitor Disks &amp; Filesystems With eBPF</title><link>https://www.netdata.cloud/blog/how-to-monitor-your-disks-and-filesystems-now-also-with-ebpf/</link><pubDate>Mon, 16 Aug 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/how-to-monitor-your-disks-and-filesystems-now-also-with-ebpf/</guid><description>&lt;!--truncate-->
&lt;div class="et_pb_module et_pb_text et_pb_text_0 et_pb_text_align_left et_pb_bg_layout_light">
&lt;div class="et_pb_text_inner">
&lt;img class="alignnone size-medium wp-image-16371" src="../wp-archive/uploads/2021/08/eBPF-monitoring-1536x932-1-600x364.png" alt="" width="600" height="364" />
&lt;h2 id="introduction-to-ebpf">Introduction to eBPF&lt;/h2>
&lt;/div>
&lt;/div>
&lt;div class="et_pb_module et_pb_text et_pb_text_1 et_pb_text_align_left et_pb_bg_layout_light">
&lt;div class="et_pb_text_inner">
&lt;p>Current IT monitoring software lacks the necessary metrics for minimizing downtime for systems and applications. Most provide system and application metrics but there is much more than this required for properly monitoring your infrastructure. With &lt;a title="eBPF" href="https://ebpf.io/" target="_blank" rel="noopener">eBPF&lt;/a> there is a technological advancement that allows monitoring software to provide rich information from the Linux kernel and present it. eBPF monitoring, specifically, provides a better understanding of what exactly is occurring on internal systems, which helps to identify where performance improvements can be made.&lt;/p></description></item><item><title>Container deployment showdown: Docker or Kubernetes?</title><link>https://www.netdata.cloud/blog/container-deployment-showdown-docker-or-kubernetes/</link><pubDate>Wed, 24 Mar 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/container-deployment-showdown-docker-or-kubernetes/</guid><description>&lt;!--truncate-->
&lt;div class="et_pb_module et_pb_text et_pb_text_0 et_pb_text_align_left et_pb_bg_layout_light">
&lt;div class="et_pb_text_inner">
&lt;img class="alignnone wp-image-16433 size-large" src="../wp-archive/uploads/2022/03/Kubernetes_vs_Docker-1200x828.png" alt="" width="1200" height="828" />
&lt;p>Monitoring the current state and performance of applications is critical for IT Ops and DevOps teams alike. Understanding the health of an application is one of the most effective ways of anticipating potential bottlenecks or slowdowns, yet it’s one of the largest challenges faced by many organizations that build and deploy software. This is largely due to applications’ distributed and diversified nature. A single outage has the potential to interrupt entire processes that, at times, can interfere with business as a whole and result in a negative effect on the bottom line.&lt;/p></description></item><item><title>5 DevOps best practices to reinforce with monitoring tools</title><link>https://www.netdata.cloud/blog/devops-best-practices-monitoring-tools/</link><pubDate>Thu, 18 Feb 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/devops-best-practices-monitoring-tools/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-medium wp-image-16441" src="../wp-archive/uploads/2022/03/devops-best-practices-monitoring-tools-v2-600x414.png" alt="" width="600" height="414" />
&lt;p>As part of a modern software development team, you’re asked to do a lot. You’re supposed to build faster, release more frequently, crush bugs, and integrate testing suites along the way. You’re supposed to implement and practice a strong DevOps culture, &lt;a href="https://github.com/upgundecha/howtheysre" target="_blank" rel="noopener noreferrer">read entire novels&lt;/a> about SRE best practices, go &lt;a href="https://en.wikipedia.org/wiki/Agile_software_development" target="_blank" rel="noopener noreferrer">agile&lt;/a>, or add a bunch of Scrum ceremonies to everyone’s calendar. Every week, the industry recommends that you “&lt;a href="https://devops.com/devops-shift-left-avoid-failure/" target="_blank" rel="noopener noreferrer">shift-left&lt;/a>” another part of the &lt;a href="https://staging-www.netdata.cloud/blog/agile-static-analysis/" target="_blank" rel="noopener noreferrer">DevOps pipeline&lt;/a>, to the point where you’re supposed to handle everything from unit testing to production deployment optimization from day one.&lt;/p></description></item><item><title>Introduction to StatsD</title><link>https://www.netdata.cloud/blog/introduction-to-statsd/</link><pubDate>Wed, 03 Feb 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/introduction-to-statsd/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-medium wp-image-16449" src="../wp-archive/uploads/2022/03/StatsD-600x414.png" alt="" width="600" height="414" />
&lt;p>StatsD is an industry-standard technology stack for monitoring applications and instrumenting any piece of software to deliver custom metrics. The StatsD architecture is based on delivering the metrics via UDP packets from any application to a central statsD server. Although the original StatsD server was written in Node.js, there are many implementations today, with Netdata being one of them.&lt;/p>
&lt;p>StatsD makes it easier for you to instrument your applications, delivering value around three main pillars: open-source, control, and modularity. That’s a real windfall for full-stack developers who need to code quickly, troubleshoot application issues on the fly, and often don’t have the necessary background knowledge to use complex monitoring platforms.&lt;/p></description></item><item><title>Actionable Alerts With Fewer False Positives</title><link>https://www.netdata.cloud/blog/actionable-intelligent-alerts/</link><pubDate>Thu, 21 Jan 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/actionable-intelligent-alerts/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-medium wp-image-16460" src="../wp-archive/uploads/2022/03/intelligent-alarms-600x413.png" alt="" width="600" height="413" />
&lt;p>Think about any sport or competitive activity, whether that’s football or a spelling bee. They always feature at least one person who acts as a moderator, referee, or judge. With their domain expertise, this person watches everyone’s behavior and constantly compares that against a set of rules. If someone crosses that threshold, they blow a whistle or throw up a flag. They are, in effect, saying that things have gone from &lt;strong>OK&lt;/strong> to &lt;strong>not OK&lt;/strong>.&lt;/p></description></item><item><title>Four key metrics for responding to IT incidents and failures</title><link>https://www.netdata.cloud/blog/four-key-metrics-for-responding-to-it-incidents-and-failures/</link><pubDate>Thu, 07 Jan 2021 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/four-key-metrics-for-responding-to-it-incidents-and-failures/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone wp-image-16474 size-large" src="../wp-archive/uploads/2021/01/DevOps-Metrics-1200x862.png" alt="" width="1200" height="862" />
&lt;div class="et_pb_module et_pb_text et_pb_text_0 et_pb_text_align_left et_pb_bg_layout_light">
&lt;div class="et_pb_text_inner">
&lt;p>If you’re a veteran in this space, you probably understand the many incident response metrics and concepts, along with the many (at times exasperating) acronyms. For those new to the space, or even those with years of experience, the &lt;a title="terminology" href="https://en.wikipedia.org/wiki/List_of_computing_and_IT_abbreviations" target="_blank" rel="noopener noreferrer">terminology&lt;/a> is often overwhelming.&lt;/p>
&lt;p>If you’re one of those people who’s struggling to navigate through the world of DevOps metrics, we’ve created this article for you. In this post, we’ll cover four main incident response metrics: MTTA, MTTR, MTBF, and MTTF. Learn what these acronyms mean, how you can use them, and how you can tie these KPIs into your Netdata experience.&lt;/p></description></item><item><title>What is DevOps?</title><link>https://www.netdata.cloud/blog/what-is-devops/</link><pubDate>Thu, 19 Nov 2020 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/what-is-devops/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-full wp-image-16550" src="../wp-archive/uploads/2022/03/what-is-devops.png" alt="" width="1024" height="600" />
&lt;p>In software development, it’s important to have a team dedicated to ensuring all systems and applications maintain maximum performance and uptime. Establishing processes that limit system and application slowdowns and outages while expediting the product release process is often done through a developer operations team, also known as &lt;em>dev ops&lt;/em> or &lt;em>DevOps&lt;/em>.&lt;/p>
&lt;p>DevOps teams are responsible for improving communication and collaboration across engineering teams to increase an organization’s ability to efficiently deliver products and services that serve the end-user. In this post, we’ll describe the different elements of DevOps, including what DevOps is, how it works, and how Netdata helps DevOps teams succeed.&lt;/p></description></item><item><title>The reality of Netdata’s long-term metrics storage database</title><link>https://www.netdata.cloud/blog/the-reality-of-netdatas-long-term-metrics-storage-database/</link><pubDate>Mon, 12 Oct 2020 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/the-reality-of-netdatas-long-term-metrics-storage-database/</guid><description>&lt;!--truncate-->
&lt;p>The perception that Netdata is only capable of short-term metrics storage is a myth. It’s a pervasive myth we still see in blog posts and through community engagement, despite it being false for more than a year.&lt;/p>
&lt;p> &lt;/p>
&lt;p>However, like all myths, this one on metrics storage began with a kernel of truth. When Netdata first flourished as an &lt;a title="open-source project" href="https://github.com/netdata/netdata" target="_blank" rel="noopener noreferrer">open-source project&lt;/a> in 2017 and 2018, the default metrics database was RAM-only. You could configure this database’s size, but for many users, that size was limited by the amount of RAM they were willing to allocate for metrics storage. We also kept the default value low to ensure Netdata worked efficiently on all hardware and a variety of operating systems.&lt;/p></description></item><item><title>Software Extensibility Is Key To Adoption</title><link>https://www.netdata.cloud/blog/software-extensibility-is-key-to-adoption/</link><pubDate>Fri, 25 Sep 2020 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/software-extensibility-is-key-to-adoption/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-full wp-image-16613" src="../wp-archive/uploads/2022/03/Software-Extensibility-Blog-Post.png" alt="" width="969" height="638" />
&lt;p>As with most commercial products, software today is mass produced for reasons of simple economics. But making the same software work for as many people as possible while also meeting the unique requirements different people and organizations have is a challenging task.&lt;/p>
&lt;p>The strategies used today to provide extensibility at cost and at the level required by various enterprises are very similar to the ones used in the 80s and 90s, when PCs first took off and captured an enormous amount of the home computing market, and when open source software started gaining popularity.&lt;/p></description></item><item><title>Metric Correlations: Detect Patterns &amp; Anomalies</title><link>https://www.netdata.cloud/blog/netdata-cloud-metric-correlations/</link><pubDate>Wed, 16 Sep 2020 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/netdata-cloud-metric-correlations/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-large wp-image-16623" src="../wp-archive/uploads/2022/03/Cloud-Correlations@2x-1200x826.png" alt="" width="1200" height="826" />
&lt;p>Today, we are excited to launch our first Netdata Cloud Insights feature, Metric Correlations, developed for discovering underlying issues more quickly and identifying the root cause more efficiently. Read on to learn more about our approach to developing this new feature, how it works, and the many benefits you’ll find incorporating this into your team’s troubleshooting workflow.&lt;/p>
&lt;h2>Some background&lt;/h2>
Let’s start with a bit of a disclaimer. It seems machine learning (ML) (or “Artificial Intelligence,” if you are looking for more LinkedIn likes) has gone mainstream in the last few years, and we are probably by now somewhere near the “Peak of Inflated Expectations” on the &lt;a title="hype cycle" href="https://en.wikipedia.org/wiki/Hype_cycle" target="_blank" rel="noopener noreferrer">hype cycle&lt;/a>. It is in this context that we want to be clear about what our goals are in this space and our approach to releasing data-driven features that draw on techniques from statistics and ML. In short, we want to be clear, open, realistic, and avoid buzzwords at all costs!
&lt;p>Over the next 12 months, we are hoping to begin building a layer of intelligence&lt;sup>&lt;a href="https://staging-www.netdata.cloud/blog/netdata-cloud-metric-correlations/#1">1&lt;/a>&lt;/sup> throughout Netdata (both Cloud and Agent) to assist with “&lt;a title="human in the loop" href="https://hai.stanford.edu/blog/humans-loop-design-interactive-ai-systems" target="_blank" rel="noopener noreferrer">human in the loop&lt;/a>” troubleshooting, mainly to help users more easily surface slowdowns, anomalies, or other issues and lower your &lt;a title="cognitive load" href="https://en.wikipedia.org/wiki/Cognitive_load" target="_blank" rel="noopener noreferrer">cognitive load&lt;/a>&lt;sup>&lt;a href="https://staging-www.netdata.cloud/blog/netdata-cloud-metric-correlations/#2">2&lt;/a>&lt;/sup> as you troubleshoot using Netdata. Simply put, we’re working to streamline your mean time to resolution (MTTR).&lt;/p></description></item><item><title>The Netdata Community Powered by NodeBB</title><link>https://www.netdata.cloud/blog/the-netdata-community-powered-by-nodebb/</link><pubDate>Thu, 13 Aug 2020 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/the-netdata-community-powered-by-nodebb/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-large wp-image-16658" src="../wp-archive/uploads/2022/03/NodeBB-1-1200x877.png" alt="" width="1200" height="877" />
&lt;p>We recently adopted &lt;a title="NodeBB" href="https://nodebb.org/" target="_blank" rel="noopener noreferrer">NodeBB&lt;/a> as our software of choice for building &lt;a title="the Netdata Community" href="https://community.netdata.cloud/" target="_blank" rel="noopener noreferrer">the Netdata Community&lt;/a>. We have &lt;a title="many good reasons" href="https://staging-www.netdata.cloud/blog/the-netdata-community/" target="_blank" rel="noopener noreferrer">many good reasons&lt;/a> for why we wanted to provide our community with a proper home online, but I wanted to cover some of the technical reasons for choosing NodeBB for our platform, and the many parallels between the NodeBB and Netdata projects, which was certainly a driving force behind this decision.&lt;/p></description></item><item><title>Why Netdata picked VerneMQ</title><link>https://www.netdata.cloud/blog/why-netdata-picked-vernemq/</link><pubDate>Tue, 14 Jul 2020 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/why-netdata-picked-vernemq/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-full wp-image-16705" src="../wp-archive/uploads/2022/03/Blog-Why-Netdata-Picked-VerneMQ.jpeg" alt="" width="683" height="470" />
&lt;p>In 2019, the Netdata team already knew that a Netdata Cloud solution in the form of an online platform would greatly complement Netdata’s distributed monitoring by making it much easier to organize large infrastructures and by enabling new ways for teams to collaborate. The old node registry available at the time wasn’t enough for Netdata’s users.&lt;/p>
&lt;p>Building an online platform, even one that does not directly process users’ metrics, is challenging. But less challenging than it was even a few years ago, since the technology stack has improved greatly over the years.&lt;/p></description></item><item><title>What is Infrastructure Monitoring?</title><link>https://www.netdata.cloud/blog/what-is-infrastructure-monitoring/</link><pubDate>Tue, 30 Jun 2020 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/what-is-infrastructure-monitoring/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-medium wp-image-16343" src="../wp-archive/uploads/2022/03/Blog-What_is_Infrastructure_Monitoring_Header-600x450.png" alt="" width="600" height="450" />
&lt;p>IT is advancing blazingly fast. To keep up with architectural changes and hybrid environments, it’s more important than ever to maintain efficient infrastructure monitoring and troubleshooting. Adding to the complexity is the increase of distributed systems, comprised of many components and services. For IT teams to effectively manage monitoring modern infrastructure, it’s necessary to have the right practices and tools in place that enable teams to do their jobs as quickly as possible with fewer resources.&lt;/p></description></item><item><title>The role of shift-left testing in an agile environment</title><link>https://www.netdata.cloud/blog/agile-static-analysis/</link><pubDate>Tue, 14 Apr 2020 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/agile-static-analysis/</guid><description>&lt;!--truncate-->
&lt;img class="alignnone size-large wp-image-16723" src="../wp-archive/uploads/2022/03/Netdata-Security-use-with-Static-Analysis-1200x899.png" alt="" width="1200" height="899" />
&lt;p>With the rapid growth of security threats to infrastructure, it’s more important than ever to proactively address vulnerabilities. As an open-source project, built on the trust of users and contributors, Netdata has security concerns at its core.&lt;/p>
&lt;p>Because we’re committed to code security and quality, we apply &lt;a href="https://agilemanifesto.org/">Agile principles&lt;/a> throughout the software development process. A component of this includes regular static analysis. Through continuous, automated testing, we’re able to move quickly to keep up with end-user requests without compromising our source code.&lt;/p></description></item><item><title>Agile Team Safety Harness With cmocka &amp; FOSS</title><link>https://www.netdata.cloud/blog/agile-team-cmocka-foss/</link><pubDate>Tue, 26 Nov 2019 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/agile-team-cmocka-foss/</guid><description>&lt;!--truncate-->
&lt;p>Netdata is made up from agile teams who are deeply committed to improving the usability of our product. We want to respond to our users and introduce in-demand features. Working directly with our community is the best way to make Netdata better.&lt;/p>
&lt;p> &lt;/p>
&lt;p>But we face the same the dilemma as all agile teams: &lt;strong>How do we do this safely?&lt;/strong>&lt;/p>
&lt;p>Safety means that we can move quickly without compromising the quality of our code. Because we want to move quickly, engage with our users’ desires, and keep quality high, we’re becoming very serious about adopting unit testing in our work.&lt;/p></description></item></channel></rss>