Context Setup
Interviews you to set up and improve a project's context for incident response: checks the integrations, imports services into the Context Graph, writes skills for the project's agents, and scores how ready it is.
How it works
- Runs when: you start it, on day 0 to set a project up, then again on day 1, in week 1 and whenever your systems change. Each run continues from the readiness report the last one left.
- Takes stock: reads the project's connections and checks that each returns data, then its skills, integration context forms, old guides and the Context Graph.
- Agrees the domains and sources of truth: proposes which domains the project holds from your teams,
CODEOWNERS, paging services and channels, and where the truth about services, owners and dependencies lives (a CMDB, PagerDuty, a service catalog,CODEOWNERS, Kubernetes, a wiki page). - Interviews you: one category at a time (components, alerts, logs, metrics, runtime, code, deploys, data stores, tickets, comms, incident history). It explores each integration first, so you confirm what it found instead of describing it.
- You approve: each skill before it is committed, and each Context Graph import before it is written.
- You get: tested skills for each integration and component, written for an agent in the middle of an incident; the domain's team, services, owners and dependencies in the Context Graph; and a readiness score out of 100 with the pending work in order and one recommended next step.
What it scores
| Area | Points |
|---|---|
| Integrations return data | 10 |
| Domains and owners | 10 |
| Service inventory | 15 |
| Integration skills, with tested queries | 20 |
| Architecture and component skills | 15 |
| Code mapped to components | 10 |
| Alerts map to services | 10 |
| Incident history, and a proven run on a past incident | 10 |
It also says how ready the project is for code review and for questions about your systems.
What it needs
- Your code host (GitHub, GitLab, Bitbucket or Azure DevOps): read repositories,
CODEOWNERSand deploy workflows - Observability (Datadog, Grafana, Prometheus or similar): read logs and metrics to test each query it writes down
- Alerts and tickets (PagerDuty, Jira, ServiceNow): read services, assignment groups and past incidents
- Anything else you connect: it uses whatever is there, and gives you a connect link for what is missing