DevOps
Advanced
DevOps skill is available on the Advanced plan. See Pricing.
Deployment health, change risk, incident triage — when the page goes off and you need an answer in three minutes.
What DevOps in Escher covers
| Capability | Example question |
|---|---|
| Change correlation | "What deployment / config change correlates with this latency spike?" |
| Incident triage | "What caused this incident?" / "What's the blast radius?" |
| Deployment health | "Are any prod deploys in the last hour failing health checks?" |
| Change risk scoring | "Rate the risk of this PR before we merge." |
| MTTR analysis | "Which incident categories take us longest to resolve, and why?" |
| Cross-team coordination | "Who is on call for the service that owns this resource?" |
Sample answers
"What changed in production in the last 90 minutes?"
Returns a ranked diff: deploys, config changes, IAM updates, infrastructure modifications — ranked by risk and grouped by service.
"What caused checkout-api latency to triple at 14:23?"
Returns an incident Canvas with a timeline, the responsible change, the metric correlation, and a suggested remediation (often: revert the deploy).
"Why are we slower at recovering from incidents than last quarter?"
Returns an MTTR analysis: which categories regressed, what's different, and what to investigate.
Where DevOps integrates
Escher pulls signals from:
- Deployment systems (GitHub Actions, GitLab CI, Argo, Spinnaker, Jenkins)
- Observability platforms (your existing metrics, traces, logs)
- Incident systems (PagerDuty, Opsgenie)
- Source control (commits, PRs, authors)
If you have any of these connected, the resulting Canvases are richer.
See the Integrations section for setup.
Tips
TIP
Anchor to a time window. "In the last 90 minutes," "since 14:00 UTC" — Escher uses the window to filter.
TIP
Name the symptom precisely. "Latency on checkout-api" is better than "things are slow."
What's next
- Incident Questions
- Pricing — Advanced plan details
- PagerDuty integration