World map

 

BM: Baca dalam Bahasa Melayu

World O3: Alarms & Screens

Runbooks

You will learn: to give every alert a fix-it card that a sleepy person can follow.

Checked with Prometheus 3 on 1 Nov 2026

The problem

3 a.m. Your first night on call. The bell says QueueTooLong. What do you wish you had?

Pick one answer.

Watch

Top of the runbook first. Put these in order. Use the arrows, or drag.

  • Still bad after 15 minutes? Call the next person
  • Make it safe: open a second counter
  • Check first: which stall, since when
  • What this alert means

A runbook: The fix-it card next to the bell: what this alert means, what to check first and how to make it safe. is the fix-it card next to the bell. Put its parts in order.

Check

Pick the message on-call reads. Use the slider to see it at 15m.

Build an alert rule from the blocks. The timeline shows when it would wait and when it would fire.

When (expr)
Wait first (for)
Labels
Message (annotations)
Your rule: rules.yml
groups:
- name: kedai
rules:
- alert: QueueTooLong
expr: kedai_queue_length > 50
for: 3m
labels:
severity: ticket
annotations:
summary: Queue alert
The value the alert watches
02550751000s5m10m15m20mthreshold 50
Graph as a table
Graph as a table
Timekedai_queue_length{stall="nasi-lemak"}
0s5
1m8
2m12
3m10
4m9
5m14
6m20
7m35
8m55
9m60
10m64
11m70
12m72
13m75
14m78
15m80
16m82
17m85
18m86
19m88
20m90

What the alert does over time

Grey: quiet. Amber: pending (true, but waiting). Red: firing.

  • {severity="ticket", stall="nasi-lemak"}

    ⏳ pending 8m to 10m · 🔔 firing 11m to 20m

At 15m:

  • FIRING QueueTooLong severity="ticket", stall="nasi-lemak"Queue alert
Timeline as a table
Time{severity="ticket", stall="nasi-lemak"}
0squiet
1mquiet
2mquiet
3mquiet
4mquiet
5mquiet
6mquiet
7mquiet
8m⏳ pending
9m⏳ pending
10m⏳ pending
11m🔔 firing
12m🔔 firing
13m🔔 firing
14m🔔 firing
15m🔔 firing
16m🔔 firing
17m🔔 firing
18m🔔 firing
19m🔔 firing
20m🔔 firing

Check

Swipe right for a good runbook step. Swipe left for one that needs work.

Swipe right for good, left for needs work. Or use the buttons.

1 / 4

Open the Queue panel and find the stall named in the alert.

Open the Queue panel and find the stall named in the alert.

You did it!

You can now give every alert a runbook a sleepy person can follow.

Go deeper (optional)

Keep runbooks in Git, next to the rules. After each incident, fix the step that confused you. No runbook yet? The alert may not be ready to page anyone.