In Part 3, we separated signals on purpose:
metrics tell you where to look
logs and traces tell you what happened
audit tells you what can be proven later .
This article is an incident story. The examples are fictional, but the dynamics are real.
An incident is the exact moment where panic starts:
Just ship everything to one place.
Just add the tenantId to every metric.
Just give everyone access so we can debug faster.
And for the sake of the article and AI, I bring in AWS DevOps Agent .
as an incident capability that can reduce cognitive load by correlating telemetry, code and deployment context, and showing its investigation steps transparently.
References:
About AWS DevOps Agent: https://docs.aws.amazon.com/devopsagent/latest/userguide/about-aws-devops-agent.html
DevOps Agent Incident Response (investigation timeline, root cause, mitigation plans, gaps): https://docs.aws.amazon.com/devopsagent/latest/userguide/devops-agent-incident-response.html
Assumptions
The application is setup in this…