<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deployment Strategies on Netdata</title><link>https://www.netdata.cloud/tags/deployment-strategies/</link><description>Recent content in Deployment Strategies on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 22 Aug 2026 05:09:03 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/deployment-strategies/index.xml" rel="self" type="application/rss+xml"/><item><title>Zero-Downtime Monitoring For Real-Time Deployments</title><link>https://www.netdata.cloud/features/architecture/zero-downtime-monitoring/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/features/architecture/zero-downtime-monitoring/</guid><description>Netdata&amp;rsquo;s distributed architecture eliminates single points of failure in monitoring, delivering sub-2-second visibility with automatic failover, zero data loss, and production-safe resource overhead—ensuring complete observability during the moments that matter most.</description></item><item><title>Fix Helm Chart Rollback &amp; Pending-Upgrade Failures</title><link>https://www.netdata.cloud/academy/helm-chart-rollback-failures/</link><pubDate>Fri, 15 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/academy/helm-chart-rollback-failures/</guid><description>&lt;p&gt;It’s a scenario that every Kubernetes operator dreads. A production deployment has gone wrong, you confidently initiate a Helm rollback, and then&amp;hellip; nothing. The command hangs, and a quick check reveals the dreaded &lt;code&gt;pending-rollback&lt;/code&gt; status. Your application is now in a broken state, and you&amp;rsquo;re blocked from deploying any new fixes. This is more than a minor inconvenience; it&amp;rsquo;s a critical failure that can leave your services unstable and your deployment pipeline paralyzed.&lt;/p&gt;</description></item><item><title>Blue-Green And Canary Deployments With NGINX</title><link>https://www.netdata.cloud/academy/blue-green-canary-deployments-nginx/</link><pubDate>Tue, 12 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/academy/blue-green-canary-deployments-nginx/</guid><description>&lt;p&gt;The moment of truth arrives. You&amp;rsquo;ve tested the new version of your application, the container image is pushed, and the deployment pipeline is ready. You click &amp;ldquo;deploy,&amp;rdquo; and a wave of anxiety hits. Will this be a smooth, zero-downtime rollout, or will your dashboards soon light up with &lt;code&gt;502 Bad Gateway&lt;/code&gt; and &lt;code&gt;504 Gateway Timeout&lt;/code&gt; errors? For many teams using advanced deployment strategies like Blue-Green or Canary, this fear is all too real.&lt;/p&gt;</description></item><item><title>What Is Canary Deployment? Benefits, Metrics &amp; Setup</title><link>https://www.netdata.cloud/academy/canary-deployment/</link><pubDate>Tue, 27 May 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/academy/canary-deployment/</guid><description>&lt;p&gt;Releasing new software versions can be a nerve-wracking experience. Even with rigorous testing, the real world of production traffic often uncovers unforeseen issues. A problematic deployment can lead to downtime, frustrated users, and a frantic scramble to roll back. This is where a canary deployment strategy shines, offering a more cautious and controlled approach to rolling out updates.&lt;/p&gt;&#10;&lt;p&gt;Instead of a big-bang release, a canary release exposes the new version to a small subset of users first, allowing you to monitor its performance and gather feedback before a full-scale rollout. This technique significantly de-risks the deployment process, especially in complex environments like Kubernetes.&lt;/p&gt;</description></item><item><title>What Is Blue-Green Deployment? Benefits &amp; Process</title><link>https://www.netdata.cloud/academy/blue-green-deployment/</link><pubDate>Sat, 24 May 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/academy/blue-green-deployment/</guid><description>&lt;p&gt;Software teams today face the challenge of releasing updates quickly without disrupting users. Traditional deployment methods often cause downtime and raise the risk of bugs reaching production. Blue green deployment offers a solution: by running two identical environments and switching traffic seamlessly, teams can deliver new versions with minimal risk and zero downtime. In this guide, we’ll explain what blue green deployment is, how it works, its benefits and challenges, and the best practices for implementing it.&lt;/p&gt;</description></item><item><title>Deployment Automation: Tools, Benefits &amp; Practices</title><link>https://www.netdata.cloud/academy/deployment-automation/</link><pubDate>Wed, 02 Apr 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/academy/deployment-automation/</guid><description>&lt;p&gt;Getting new features and bug fixes from a developer’s machine into the hands of users quickly and reliably is paramount when it comes to successful software development. Manual deployment processes, however, are often slow, error-prone, and stressful.&lt;/p&gt;&#10;&lt;p&gt;Manual tasks in application deployments frequently lead to configuration errors and make the software deployment process a time consuming process, especially for complex deployments. This is where &lt;strong&gt;deployment automation&lt;/strong&gt; comes in – a crucial practice in &lt;a href="https://www.netdata.cloud/solutions/built-for/devops/"&gt;modern DevOps&lt;/a&gt; and agile methodologies.&lt;/p&gt;</description></item><item><title>How To Achieve High Availability In CI/CD With Observability</title><link>https://www.netdata.cloud/academy/ci-cd-high-availability/</link><pubDate>Sun, 09 Jun 2024 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/academy/ci-cd-high-availability/</guid><description>&lt;p&gt;Your CI/CD pipeline is the backbone of your software delivery process. When it works, code flows smoothly from commit to production. But what happens when it breaks? A failed pipeline means stalled feature releases, delayed bug fixes, and frustrated developers unable to ship their work. To prevent this, you need to treat your CI/CD infrastructure with the same rigor as your production applications, and that starts with making it highly available.&lt;/p&gt;</description></item><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&gt;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"&gt;Netdata Cloud Terraform Provider&lt;/a&gt; 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&gt;non-production&lt;/strong&gt; installation of the Netdata Agents:&lt;/p&gt;</description></item><item><title>Netdata Best Practices</title><link>https://www.netdata.cloud/blog/netdata-best-practices/</link><pubDate>Fri, 03 Nov 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/netdata-best-practices/</guid><description>&lt;p&gt;Effective &lt;strong&gt;system monitoring&lt;/strong&gt; is non-negotiable in today&amp;rsquo;s complex IT environments. Netdata offers real-time performance and health monitoring with precision and granularity. But the key to harnessing its full potential lies in the optimization of your setup. Let’s ensure you are not just collecting data, but doing it in the most optimal way while gaining actionable insights from it.&lt;/p&gt;&#10;&lt;p&gt;The starting point for optimization is a robust setup. Netdata is engineered for minimal footprint and can run on a wide range of hardware—from IoT devices to powerful servers. Time for a deep dive into each of these key areas and what the best practices you should follow, if you are serious about monitoring and optimizing your Netdata monitoring setup:&lt;/p&gt;</description></item><item><title>Netdata Parents (Streaming and Replication)</title><link>https://www.netdata.cloud/blog/netdata-parents-streaming-replication/</link><pubDate>Fri, 30 Jun 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/netdata-parents-streaming-replication/</guid><description>&lt;h2 id="what-are-they-and-why-do-we-need-them"&gt;What are they and why do we need them?&lt;/h2&gt;&#10;&lt;p&gt;A “Parent” is a Netdata Agent, like the ones we install on all our systems, but is configured as a central node that receives, stores and processes metrics data from other Netdata “Child” nodes in our infrastructure.&lt;/p&gt;&#10;&lt;p&gt;Netdata Parents are flexible. You can have one big active-active cluster of Netdata Parents, or you can spread a lot of independent Parents across the infrastructure.&lt;/p&gt;</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--&gt;&#10;&lt;div class="et_pb_module et_pb_text et_pb_text_0 et_pb_text_align_left et_pb_bg_layout_light"&gt;&#10;&lt;div class="et_pb_text_inner"&gt;&#10;&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" /&gt;&#10;&lt;p&gt;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&gt;</description></item><item><title>RabbitMQ NOT_FOUND - no queue or exchange: publishing to something that does not exist</title><link>https://www.netdata.cloud/guides/rabbitmq/rabbitmq-not-found-no-queue-exchange/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/guides/rabbitmq/rabbitmq-not-found-no-queue-exchange/</guid><description>&lt;p&gt;Your publisher or consumer logs show &lt;code&gt;NOT_FOUND - no exchange 'orders.events' in vhost '/'&lt;/code&gt;, or the queue variant, &lt;code&gt;NOT_FOUND - no queue 'billing.jobs' in vhost '/'&lt;/code&gt;. The RabbitMQ server log has the matching line: &lt;code&gt;operation basic.publish caused a channel exception not_found: no exchange 'orders.events' in vhost '/'&lt;/code&gt;. The channel that raised it is now closed, and depending on the client library, your application may be spinning in a declare-fail-reconnect loop.&lt;/p&gt;</description></item></channel></rss>