<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloudwatch on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/cloudwatch/</link><description>Recent content in Cloudwatch on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 01 Sep 2026 15:20:27 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/cloudwatch/index.xml" rel="self" type="application/rss+xml"/><item><title>Amazon CloudWatch alarms gain configurable warm-up periods</title><link>https://curadevops.metacog.co.kr/insights/2026-09-01-amazon-cloudwatch-now-supports-warm-up-periods-for-alarms/</link><pubDate>Tue, 01 Sep 2026 15:20:27 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-01-amazon-cloudwatch-now-supports-warm-up-periods-for-alarms/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> New GA WarmUpConfiguration parameter lets teams delay alarm evaluation after resource creation, reducing on-call noise from missing-data transitions during startup. Update IaC alarm definitions (Terraform/CloudFormation) to include warm-up periods for resources that take time to begin emitting metrics.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>CloudWatch agent gains native journald log collection on Linux</title><link>https://curadevops.metacog.co.kr/insights/2026-08-28-amazon-cloudwatch-agent-adds-support-for-journald-logs/</link><pubDate>Fri, 28 Aug 2026 21:17:44 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-28-amazon-cloudwatch-agent-adds-support-for-journald-logs/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Teams running Amazon Linux 2023 or other systemd-only distros no longer need disk-export workarounds to ship structured journal logs to CloudWatch. Update the CloudWatch agent to the latest version and add a journald config block to consolidate logging for those instances this quarter.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>CloudWatch Log Centralization adds tag propagation to destination log groups</title><link>https://curadevops.metacog.co.kr/insights/2026-08-20-amazon-cloudwatch-log-centralization-now-supports-log-group/</link><pubDate>Thu, 20 Aug 2026 11:19:17 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-20-amazon-cloudwatch-log-centralization-now-supports-log-group/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Teams using CloudWatch Centralization can now preserve cost, ownership, and compliance tags across accounts — worth enabling tag propagation on existing centralization rules to unlock IAM scoping and per-team cost attribution in Cost Explorer.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Tag propagation on centralized logs enables per-team observability cost attribution out of the box, which may inform how your org structures log ownership and FinOps reporting for multi-account environments.&lt;/li>
&lt;/ul></description></item><item><title>CloudWatch pipelines adds GeoIP, RDS, and XML processors (GA)</title><link>https://curadevops.metacog.co.kr/insights/2026-08-20-amazon-cloudwatch-pipelines-adds-geoip-rds-and-xml-processor/</link><pubDate>Thu, 20 Aug 2026 11:19:17 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-20-amazon-cloudwatch-pipelines-adds-geoip-rds-and-xml-processor/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> GA additions to CloudWatch pipelines reduce the need for custom log-transformation Lambda functions or external processors; evaluate replacing any bespoke RDS/XML parsing glue with these managed processors during the next observability stack review.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> GA announcement&lt;/li>
&lt;/ul></description></item><item><title>Amazon WorkSpaces adds enhanced CloudWatch observability metrics</title><link>https://curadevops.metacog.co.kr/insights/2026-08-07-amazon-workspaces-now-publishes-enhanced-observability-metri/</link><pubDate>Fri, 07 Aug 2026 00:23:45 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-07-amazon-workspaces-now-publishes-enhanced-observability-metri/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> New free CloudWatch metrics for WorkSpaces cover network, compute, storage, and session health — worth incorporating into dashboards if your org runs WorkSpaces as part of the platform, but no migration or deadline required.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>AWS Lambda Managed Instances capacity providers now log to CloudWatch</title><link>https://curadevops.metacog.co.kr/insights/2026-07-25-aws-lambda-now-publishes-logs-for-lambda-managed-instances-c/</link><pubDate>Sat, 25 Jul 2026 11:58:38 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-25-aws-lambda-now-publishes-logs-for-lambda-managed-instances-c/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> If your org uses Lambda Managed Instances for high-volume EC2-backed workloads, structured JSON lifecycle logs (launches, terminations, health checks) are now auto-enabled in CloudWatch — useful context for diagnosing provisioning issues, but no action required since it ships on by default.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>CloudWatch adds AI coding agent observability dashboard (GA)</title><link>https://curadevops.metacog.co.kr/insights/2026-07-21-amazon-cloudwatch-announces-coding-agent-insights/</link><pubDate>Tue, 21 Jul 2026 12:20:39 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-21-amazon-cloudwatch-announces-coding-agent-insights/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> New GA CloudWatch feature ingesting OpenTelemetry metrics from coding agents; no infrastructure changes required, but platform engineers who own the observability stack should note it as a new dimension of telemetry available alongside existing operational data.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Directly addresses AI coding tool ROI governance — token spend, commit throughput, PR velocity, and cost-per-model comparisons; evaluate enabling Coding Agent Insights this quarter to inform decisions on expanding or right-sizing AI tool access across teams.&lt;/li>
&lt;/ul></description></item><item><title>Amazon CloudWatch Logs adds intelligent storage tiering (3 tiers)</title><link>https://curadevops.metacog.co.kr/insights/2026-07-16-amazon-cloudwatch-logs-announces-intelligent-tiering-for-sto/</link><pubDate>Thu, 16 Jul 2026 12:15:50 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-16-amazon-cloudwatch-logs-announces-intelligent-tiering-for-sto/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> New GA capability that can eliminate the need to export verbose logs to S3 or filter them for cost reasons — evaluate enabling account-level intelligent tiering this quarter to simplify your observability stack and reduce log storage spend.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> This changes the unit economics of CloudWatch log retention, making it viable to keep high-volume logs natively rather than running export pipelines to cheaper storage; include in the next FinOps/observability cost review cycle.&lt;/li>
&lt;/ul></description></item></channel></rss>