<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monitoring on Cloudkaramchari</title><link>https://www.cloudkaramchari.com/categories/monitoring/</link><description>Recent content in Monitoring on Cloudkaramchari</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>cloudkaramchari</copyright><lastBuildDate>Mon, 10 Aug 2026 23:00:00 +0530</lastBuildDate><atom:link href="https://www.cloudkaramchari.com/categories/monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>CloudWatch Managed Prometheus Collectors: Setup Guide for EC2 and ECS</title><link>https://www.cloudkaramchari.com/blog/cloudwatch-managed-prometheus-collectors-setup-guide/</link><pubDate>Mon, 10 Aug 2026 23:00:00 +0530</pubDate><guid>https://www.cloudkaramchari.com/blog/cloudwatch-managed-prometheus-collectors-setup-guide/</guid><description>
&lt;h1 id="cloudwatch-managed-prometheus-collectors-setup-guide-for-ec2-and-ecs">CloudWatch Managed Prometheus Collectors: Setup Guide for EC2 and ECS&lt;/h1>
&lt;p>If you've been running your own OpenTelemetry Collector just to get Prometheus metrics into CloudWatch, AWS shipped the fix in late July 2026: &lt;strong>managed Prometheus collectors&lt;/strong>. You hand CloudWatch a scrape config and a VPC connection, and it provisions, scales, and runs the scraper for you — no EC2 instance or Fargate task babysitting a Collector binary. This walks through actually setting one up for EC2 and ECS targets, not just the announcement.&lt;/p></description></item></channel></rss>