PagerMate documentation
Practical guides for setting up your workspace, managing incidents, and connecting monitoring.
What would you like to do?
Set up your workspace
A complete setup from agents to your first API incident.
Handle an incident
Acknowledge, investigate, comment, and resolve.
Plan on-call coverage
Build rotations and handle absences without losing visibility.
Connect your monitoring
Copy working Bash examples and understand deduplication.
How the pieces fit together
| Item | What it represents | Example |
|---|---|---|
| Agent | A person who responds | An infrastructure engineer |
| Schedule | An ordered on-call rotation | Weekly platform coverage |
| Override | Temporary replacement for a schedule | Cover Tuesday afternoon |
| Vacation | Whole days an agent is unavailable | Annual leave |
| Escalation policy | Ordered levels containing agents or schedules | Primary coverage, then backup |
| Service | The application or infrastructure being monitored | Production database |
| Incident | An issue and its investigation history | Database connection failures |
A service connects to an escalation policy. A policy level can point to an individual agent or to a schedule. The schedule determines who is on call for that time.
Current notification status
Incident creation, history, status changes, schedules, overrides, and reporting work. Automatic incident notification delivery and escalation execution are not active yet. Configuring a policy or saving notification preferences does not currently send email, SMS, push notifications, or calls. See Notification settings.
Find an answer
Use the search button to search these guides. For common problems, start with Troubleshooting. For help from the team, see Contact support.
Machine-readable documentation
- Sitemap: homepage and documentation URLs, with source modification dates, change frequencies, and page priorities.
- llms.txt: the index generated by Fumadocs.
- llms-full.txt: the complete documentation in one text file.
These files regenerate from the current documentation when it is published.