CASE 91 · HAWTHORN · 2024
CloudWatch metrics, streamed centrally, queryable everywhere.
A B2B platform had observability per account — each team kept its own CloudWatch dashboards in its own account. Cross-account incident correlation took an engineer half a day per incident. We turned on CloudWatch Metric Streams across the org and landed everything in a central Prometheus-compatible store.
B2B platform
LANDING ZONE
2024
RESULTS
What changed, by the numbers.
CROSS-ACCOUNT CORRELATION
< 2m
ACCOUNTS STREAMING
29
INCIDENT MTTR
−38%
METRIC RETENTION
13 MONTHS
HOW IT WENT
Cross-account incidents were the painful ones. The customer-facing API in account A was timing out; the database in account B was slow; the queue in account C was backed up. Three accounts, three CloudWatch consoles, three engineers swapping screenshots in Slack.
Metric Streams pushed every account’s metrics to a central Firehose, with Prometheus-format conversion at the Kinesis Data Stream consumer. Managed Grafana on top sat in one place; engineers built dashboards that spanned accounts as easily as services.
Cross-account correlation time dropped from half a day to under two minutes. Incident MTTR on cross-account incidents fell 38%. The "swap screenshots in Slack" pattern got replaced with "share this Grafana link."
RELATED · SAME DOMAIN
Other engagements in this space.
READY WHEN YOU ARE
Let's get your AWS bill (and architecture) in order.
The discovery call is free. You walk away with at least one concrete idea — even if we never work together.