New to Kestra?
Use blueprints to kickstart your first workflows.
When a CloudWatch metric breaches, auto-collect metric context and run diagnostics, then post a triage bundle to Slack. Built for on-call engineers.
A "CPU > 80%" alert with zero context is where incidents go to waste time. The on-call engineer opens the alert, then spends twenty minutes clicking through CloudWatch, logs, and the console to figure out what's actually wrong. This blueprint does that triage automatically the moment the metric fires.
On-call engineers, SREs, and platform teams who want CloudWatch alarms to be the start of the investigation, not a treasure hunt.
Wiring this with EventBridge + Lambda means scattered code and no visibility. As a Kestra flow the triage logic is declarative YAML the whole team can read, every run is logged and replayable, and adding a new diagnostic is one line in the diagnostic_commands input.
cloudwatch:GetMetricStatistics plus read permissions for whatever your diagnostic commands touch (e.g. ec2:DescribeInstances, logs:FilterLogEvents).AWS_ACCESS_KEY_ID: AWS access key for the CloudWatch and diagnostic API calls.AWS_SECRET_ACCESS_KEY: AWS secret key for the CloudWatch and diagnostic API calls.SLACK_WEBHOOK_URL: Incoming webhook URL for the triage alert.metric_namespace, metric_name, and your read-only diagnostic_commands.runbook_url.If branch that pages via PagerDuty when diagnostics show a hard failure.