Automatic Runbooks
Runbooks suggests the runbook that fits each incident. The L1 Agent matches your runbooks to the incident; on Suggests, nothing runs. To run runbook steps, connect an On-Prem Worker and let the capability act on its own.
How runbook matching works
The agent ingests runbooks from your source of record. See Onboard the L1 Agent for the supported sources.
For each incident, it picks the runbook that applies and composes a scoped set of steps.
On Suggests, it shows the matching runbook. [VERIFY] Where the suggestion appears.
Add runbooks after setup
Turn on Runbooks during setup, then add the runbooks themselves in Runbooks in ADR mission control once the agent is live.
Settings
Setting | Behavior |
|---|---|
Manually triggered + Suggests | Starting value. Suggests a runbook when someone triggers the agent. Nothing runs. |
Every incident + Suggests | Suggests a runbook on every new incident. Nothing runs. |
Every incident + Acts on its own | [VERIFY] Runs the runbook's context-collection steps through the On-Prem Worker. Remediation steps still need explicit approval. |
Off | Does not run. [VERIFY] |
Running runbook steps
Running steps requires the On-Prem Worker in your environment. For how the worker connects and what it can run, see Onboard the L1 Agent.
Mode | What happens | Approval |
|---|---|---|
Context collection | Read-only diagnostic steps. The agent uses the results in its reasoning. | Not required |
Remediation actions | Corrective action such as restarting a service or clearing a queue. | Explicit approval required |
Source: Manage incidents with the L1 Agent.
Next steps
Install the On-Prem Worker.
Learn how runbooks work with your automation platform in Manage incidents with the L1 Agent.
Change runbook settings in Configure the L1 Agent.