Skip to content

Commit

Permalink
Update op-monitorism/faultproof_withdrawals/runbooks/RUNBOOK.md
Browse files Browse the repository at this point in the history
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
  • Loading branch information
raffaele-oplabs and coderabbitai[bot] authored Nov 4, 2024
1 parent 99a4d65 commit ab9a877
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion op-monitorism/faultproof_withdrawals/runbooks/RUNBOOK.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ This runbook may contain references to actions and specifications not included i
The mechanism and the content of the alert is not yet published, so the name of the alerts and the contents of the alerts will depend on your own setup.

## Automated runbooks
Along side this runbook we have some "automated" runbooks. These runbooks can be used to execute some actions either during triaging of an alert or during containement of an incident. These are basically [Jupiter notebooks](https://jupyter.org/), a mix of executable code and markdown, that makes them perfect for putting together instructions and "executable instructions"
Along side this runbook we have some "automated" runbooks. These runbooks can be used to execute some actions either during triaging of an alert or during containement of an incident. These are basically [Jupyter notebooks](https://jupyter.org/), a mix of executable code and markdown, that makes them perfect for putting together instructions and "executable instructions". For setup instructions, see the [README](./automated/README.md).
Automated runbooks are in the **automated** subfolder.
Each runbook is useful for a specific task. After starting the runbook make sure you select the one you need to execute.

Expand Down

0 comments on commit ab9a877

Please sign in to comment.