Skip to main content

Monitor Mesh

4 regions60s checksSSL watch
Status
GetPulseCheckLive

Uptime Monitor

OverviewAlertsConnectPlansStatus
99.98%
Log InStart Free
Log inSign up

Monitoring Overview

Everything critical, one swipe away.

All Systems Nominal

99.98%

Fleet Health

4

Regions

60s

Checks

  • Overview

    Live uptime, latency & alert surfaces

  • Alerts

    Rules, SSL tracking & status comms

  • Connect

    Email alerts now, webhooks next

  • Plans

    Plans for side projects through teams

  • Status

    Public service health & incident history

Start FreeView Status
Documentation navigation
Documentation home
  • Getting started

    • What is GetPulseCheck?
    • Quickstart: your first monitor in 5 minutes
    • Signing up, logging in & password reset
    • Understanding the dashboard
    • Plans & limits (Starter vs Pro)
  • Monitors

    • Monitor types overview
    • Creating a monitor (auto-detect + manual)
    • HTTP/HTTPS monitor guide
    • Ping monitor guide
    • TCP port monitor guide
    • SSL certificate checksPartial
    • Probe regions & multi-region confirmation
    • Check intervalsPartial
    • Managing monitors (edit, pause, bulk-delete)
  • Alerting & notifications

    • How alerting works
    • Email alerts
    • Slack notificationsPartial
    • Webhooks (custom integrations)
    • PagerDuty integration
    • Testing alerts & recovery
  • Escalation policies

    • Escalation policies overview
    • Building a multi-step escalation policyPartial
    • Assigning a policy to a monitor
  • Incidents

    • Incident lifecycle & statuses
    • Multi-region confidence scoring
    • Acknowledging & resolving incidents
    • Sharing an incident (public link)
    • Post-incident recapPartial
  • Status pages

    • Status pages overviewPartial
    • Building & publishing your status pagePartial
    • Sharing your status pagePartial
  • Reports & exports

    • Reports overviewPartial
    • CSV export availabilityComing soon
    • Report templatesPartial
  • Team & collaboration

    • Team roles explainedPartial
    • Inviting teammatesComing soon
  • Account & security

    • Your profile & contact settings
    • Account settings & maintenance windowsComing soon
    • Security: sessions, MFA & recoveryComing soon
    • Billing & plan managementPartial
  • Reference

    • FAQ
    • Probe locations & IP allow-listingPartial
    • Glossary
    • Troubleshooting

Alerting and notifications

Test alerts and recovery

Validate a monitor's alert configuration before you depend on it during an incident, and inspect the recovery information your responders will receive.

Before testing

  • Open the monitor and enable alerts in Alert Configuration.
  • For an alert test, configure at least an email address or an alert webhook.
  • For a recovery test, enable recovery notifications and configure an email address or recovery webhook.

Test an alert

  1. Open the monitor's alert configuration.
  2. Select the alert test action.
  3. Review the returned channel payloads, including the failure reason, response context, regional confirmation, confidence, and incident link when available.

The action validates the configuration and prepares sample alert payloads. If an alert webhook is selected, GetPulseCheck sends it a test request with these markers:

  • event: monitor.alert.test
  • testEvent: true
  • liveEventType: monitor.alert

The test does not open a live incident or send a live email alert.

Test a recovery

  1. Keep alerts enabled and turn on recovery notifications.
  2. Select the recovery test action.
  3. Review the recovery payload, including outage duration, resolution time, affected regions, and the incident link when a resolved incident exists.

If there is no recent resolved incident, GetPulseCheck uses sample recovery timing and region data for the preview. The action validates the configuration and returns the payload; it does not resolve an incident or send a live recovery message.

Test PagerDuty separately

PagerDuty uses its own Send test alertaction in Account Settings. That action sends a test event to PagerDuty and updates the integration's Last tested time after success.

Related

  • How alerting works
  • Email alerts
  • Webhooks
  • PagerDuty integration
GetPulseCheck

Global website monitoring, SSL tracking, and instant incident alerts for engineering teams who care about uptime.

Product

  • Features
  • Pricing
  • Integrations
  • Status page
  • ChangelogSoon

Company

  • AboutSoon
  • BlogSoon
  • CareersSoon
  • Contact

Resources

  • Documentation
  • System status
  • FAQ

Legal

  • Privacy policySoon
  • Terms of serviceSoon
  • SecuritySoon

© 2026 GetPulseCheck. All rights reserved.

Built with ❤ for engineers who care about uptime.