CuraDevOps

tag: Cloudwatch · 8 items

2026-09-01 · AWS What's New · source ↗ #cloudwatch#observability#alerting
  • Platform/SRE — Plan: 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.
  • CI/CD — Skip
  • Leader — Skip
2026-08-28 · AWS What's New · source ↗ #cloudwatch#observability#journald
  • Platform/SRE — Plan: 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.
  • CI/CD — Skip
  • Leader — Skip
2026-08-20 · AWS What's New · source ↗ #cloudwatch#observability#aws
  • Platform/SRE — Plan: 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.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: GA announcement
2026-08-20 · AWS What's New · source ↗ #cloudwatch#observability#aws
  • Platform/SRE — Plan: 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.
  • CI/CD — Skip
  • Leader — Learn: 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.
  • Platform/SRE — Learn: 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.
  • CI/CD — Skip
  • Leader — Skip
2026-07-25 · AWS What's New · source ↗ #aws-lambda#observability#cloudwatch
  • Platform/SRE — Learn: 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.
  • CI/CD — Skip
  • Leader — Skip
2026-07-21 · AWS What's New · source ↗ #cloudwatch#ai-coding#observability
  • Platform/SRE — Learn: 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.
  • CI/CD — Skip
  • Leader — Plan: 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.
  • Platform/SRE — Plan: 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.
  • CI/CD — Skip
  • Leader — Plan: 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.