medium riskservice affecting~30 min

Runbook: Upgrade Prometheus

1 · Prerequisites

Confirm every item is in place before any state change.

New Prometheus version tarball
Current configuration in version control

2 · Pre-checks

Read-only diagnostic commands. If any of these don't match expected output, stop and investigate further.

· Read release notes for breaking changes
· Backup TSDB snapshot before upgrade
· Verify release notes compatibility with exporters

3 · Procedure

Execute each step in order. Verify the expected output of a step before moving to the next.

1Stop Prometheus
2Install new binary
3Start Prometheus
4Verify /-/ready and /-/healthy
5Verify alert rules load
6Verify targets are scraped

4 · Verification

Confirm the procedure actually fixed the problem.

✓Prometheus is on the new version
✓No breaking changes
✓All scrape targets up
✓Rules evaluate correctly

5 · Rollback

If verification fails, undo the procedure in reverse order.

↶Stop Prometheus
↶Restore old binary
↶Restore TSDB from snapshot

6 · Escalation

When the runbook isn't enough, contact:

· Coordinate with team to upgrade exporters if needed

Purpose

Upgrade Prometheus

When to use this runbook

Use this runbook when the operator needs a guided procedure to handle the situation described above.

Pre-checks

Before starting the procedure, confirm the prerequisites and pre-checks are met. The structured lists are rendered from the frontmatter by the page layout.

Procedure

Follow the steps from the frontmatter procedure steps. The page layout renders the steps as a checklist with copy-to-clipboard affordances.

Verification

After the procedure, the structured verification items from the frontmatter are rendered as a checklist.

Rollback

If the procedure fails or makes things worse, follow the structured rollback steps from the frontmatter.

Escalation

The structured escalation path is rendered from the frontmatter. Use it if the operator cannot complete the procedure safely.