<p>I am trying to set up a Prometheus CloudWatch agent to scrape metrics from Fluent Bit that is running on Amazon EKS. I am following this guide to set up a CloudWatch agent with Prometheus: <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-configure.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-configure.html</a>. In this guide prometheus agent is created as a Deployment.</p>
<p>My Fluent Bit is deployed as DaemonSet on EKS. I've read this answer that explains difference of Deployment vs DaemonSet: <a href="https://stackoverflow.com/questions/53888389/difference-between-daemonsets-and-deployments">Difference between daemonsets and deployments</a></p>
<p>But I still have hard time understanding of what is the best to use for prometheus agent. The way I see it, since Fluent Bit is a DaemonSet, I would want Prometheus agent to be a DaemonSet too to make sure it will grab metrics from those PODs that might spawn in Fluent Bit. Am I right?</p>

Bryuk
<p><code>...since Fluent Bit is a DaemonSet, I would want Prometheus agent to be a DaemonSet too to make sure it will grab metrics from those PODs that might spawn in Fluent Bit. Am I right?</code></p>
<p>This is correct in order to scrap from every FluentBit agent in your cluster and adapt to situation where node(s) scale out/in.</p>
