A Mac window setup for DevOps and on call
Terminals, dashboards, logs, the incident channel and runbooks. A layout for operations work that keeps the signal in view when something breaks.
During an incident you need the dashboard, the logs and a terminal in view together, with the incident channel and runbook one step away.
Incident layout
| Column | Width | Holds |
|---|---|---|
| 1 | Half | Dashboard |
| 2 | Half | Two terminals stacked: logs above, shell below |
| 3 | Half | Incident channel |
| 4 | Half | Runbook |
Tips
- Use separate terminal windows rather than panes so any one can sit beside the dashboard; see terminal windows.
- Stack the log tail and shell in one column with ⌃ ⌥ ] so they share its height.
- Keep the incident layout saved, and open it with a clutterfreemac:// link from your paging tool or Raycast.
Day to day, use your normal development layout; switch to the incident one in a click when the pager goes off.
Questions
What is a good window layout for on call incidents?
The dashboard and logs side by side with a shell, and the incident channel and runbook one step away.
Read next
- Guide
Taking notes during a video call on a Mac
Keep the call, your notes and the shared document in view at once on one screen: sizes that work, and how to stop the call window hiding behind others.
Read › - Guide
A Mac window setup for translators
Source text, your translation, dictionaries and term bases. A layout that keeps the source and target side by side and the references one move away.
Read › - Guide
Editor and browser side by side on a Mac, without the shuffle
Change code, look at the result. Ways to keep an editor and a browser next to each other on one Mac screen, and how to fit the dev tools in too.
Read ›