Summary
An SLO breach followed all the way down to the trace.
The tools line up with the way an on-call engineer actually moves: which services are breaching, what the SLO said it promised, then the sampled traces sitting underneath it.
What it is
An MCP server over AWS Application Signals. It reads the monitored service inventory, SLI and SLO status, CloudWatch metrics and X-Ray traces, so an investigation runs from which service is unhealthy to which spans are slow in one place.
What you get
- Every service Application Signals monitors, listed
- Health detail for one named service
- CloudWatch metrics queried for a monitored service
- SLI status and SLO compliance across all services
- The full configuration of a single SLO
- Sampled X-Ray traces for distributed tracing analysis
- Transaction spans searched in X-Ray trace data
Requirements
AWS credentials already configured, through aws configure or environment variables, plus the uv package manager. The account has to have Application Signals enabled or there is nothing to list.