<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws-Cloudwatch on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/aws-cloudwatch/</link><description>Recent content in Aws-Cloudwatch on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 15 Oct 2026 15:27:57 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/aws-cloudwatch/index.xml" rel="self" type="application/rss+xml"/><item><title>CloudWatch Pipelines adds conditional log routing and chained parsers (GA)</title><link>https://curadevops.metacog.co.kr/insights/2026-10-15-amazon-cloudwatch-announces-log-routing-and-chained-log-pars/</link><pubDate>Thu, 15 Oct 2026 15:27:57 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-15-amazon-cloudwatch-announces-log-routing-and-chained-log-pars/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> New GA CloudWatch Pipelines capabilities let you split log streams by severity, source, or type into separate log groups with distinct retention and access controls, and apply sequential parsers to nested formats. Worth evaluating this quarter if you&amp;rsquo;re using CloudWatch Pipelines or considering consolidating log routing into a managed service.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> This GA capability improves CloudWatch&amp;rsquo;s log-routing sophistication and could reduce observability costs via targeted retention policies, but it doesn&amp;rsquo;t change vendor risk, licensing, or require a strategic decision now.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> GA announcement&lt;/li>
&lt;/ul></description></item></channel></rss>