How Pingstack fits together
A check describes what should be healthy and when to evaluate it. Pingstack either receives a heartbeat from your job or actively examines a public target. Each check belongs to one account.
| Term | Meaning |
|---|---|
| Heartbeat location | A named sender with its own secret check-in URL |
| Probe location | A Pingstack region that examines a website or TCP service |
| DNS resolver | A public DNS service whose answers are compared to your expectations |
| Incident | A period of degraded or down health, resolved when the check returns up |
| Notification group | Channels and scheduled recipients assigned to checks |
| Roster | A reusable collection of account members |
| Dashboard | A collection of checks, optionally grouped and shared |
| Overview | The account-wide view that automatically includes current checks |
A useful first setup
Section titled “A useful first setup”- Select the account that should own the monitoring.
- Create a website or heartbeat check.
- Assign a notification group.
- Observe a successful result and a controlled failure/recovery.
- Organize related checks into a dashboard.
An Editor or Admin can configure checks and alerts. Public sharing and integration management need Admin access. Billing and Viewer members can inspect monitoring but cannot configure it. See the role matrix.
Do not confuse a public status URL with a heartbeat URL: the former reveals health, while the latter lets a sender report health.