<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Datadog on Opslifeuk Limited</title><link>https://opslife.co.uk/tags/datadog/</link><description>Recent content in Datadog on Opslifeuk Limited</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sat, 26 Sep 2026 09:30:00 +0100</lastBuildDate><atom:link href="https://opslife.co.uk/tags/datadog/index.xml" rel="self" type="application/rss+xml"/><item><title>Datadog on Kubernetes: A Practical Setup That Pays for Itself</title><link>https://opslife.co.uk/observability/datadog-kubernetes/</link><pubDate>Sat, 26 Sep 2026 09:30:00 +0100</pubDate><guid>https://opslife.co.uk/observability/datadog-kubernetes/</guid><description>&lt;p&gt;Datadog can see almost everything in your platform. The problem is rarely
missing data - it&amp;rsquo;s too much disconnected data, noisy alerts, and a bill that
grows faster than your traffic. A few decisions made early make the
difference between a tool your engineers trust and an expensive wall of
dashboards.&lt;/p&gt;
&lt;p&gt;This is the setup we recommend for running Datadog on Kubernetes.&lt;/p&gt;
&lt;h2 id="install-the-agent-the-kubernetes-way"&gt;Install the Agent the Kubernetes way&lt;/h2&gt;
&lt;p&gt;Deploy the Datadog &lt;strong&gt;Agent&lt;/strong&gt; as a DaemonSet (one per node) together with the
&lt;strong&gt;Cluster Agent&lt;/strong&gt;, which collects cluster-level data and takes load off the
Kubernetes API server. Either the &lt;strong&gt;Datadog Operator&lt;/strong&gt; or the official
&lt;strong&gt;Helm chart&lt;/strong&gt; will do this; pick one and keep its configuration in Git.&lt;/p&gt;</description></item></channel></rss>