Getting Started
Real-time monitoring for zero downtime
Welcome to StatusPulse
Get your infrastructure under observation in under three minutes. This guide walks you through provisioning your workspace, deploying your first HTTP endpoint checker, and routing alerts to your preferred communication channels.
StatusPulse pings your endpoints from 14 global probe locations every 30 seconds. You’ll receive instantaneous notifications via Slack, PagerDuty, or SMS the moment latency exceeds your defined thresholds or your service returns a non-2xx status code. Follow the steps below to move from registration to active monitoring.
Account Setup
Create Your Workspace
Navigate to app.statuspulse.io/register and enter your corporate email. Verify your domain via the DKIM record we generate. Once confirmed, assign a workspace name like "Acme-Prod-Infra" and select your subscription tier.
Configure API Keys
Generate a read-write API token under Settings > Integrations. Store this securely in your environment variables. You’ll need it to programmatically deploy monitors or sync with Terraform.
Set Regional Probes
By default, StatusPulse checks your endpoints from New York, Frankfurt, and Tokyo. Adjust probe regions in the Dashboard to match your primary user base and reduce false-positive latency alerts.
Your First HTTP Monitor
Deploying a monitor requires a target URL, check frequency, and alert thresholds. Follow these exact parameters for your initial setup:
Define Target & Method
Enter `https://api.yourcompany.com/v1/health` as your endpoint. Set the HTTP method to `GET`. Enable TLS certificate validation and set the expected response code to `200 OK`.
Set Check Frequency
Choose `30s` for production-critical services or `5m` for staging environments. StatusPulse will immediately begin polling from your selected probe regions upon activation.
Configure Alert Channels
Link your primary notification route under Alerts > Channels. Paste your Slack webhook URL for `#ops-incidents`, connect your PagerDuty integration key for critical escalations, or add a Twilio phone number for SMS fallback.
Set Trigger Rules
Trigger an incident if downtime persists for `2 consecutive checks` or if response time exceeds `1200ms`. Assign the rule to your newly created channels to ensure your on-call engineer receives a page within 60 seconds.
Invite Your Team
Collaborative monitoring requires role-based access control. Grant your DevOps leads `Admin` privileges to manage probe configurations, while assigning `Viewer` access to product managers who only need incident dashboards.
Navigate to Settings > Team Management and paste up to 25 email addresses. Invitees receive a secure link to join your workspace. Enable SSO via Okta or Auth0 if your organization mandates centralized identity management.
Assign Roles
Admin: Full control over monitors, alerts, and billing. Editor: Can create and modify checks. Viewer: Read-only access to status pages and incident logs.
Set Up Escalation Policies
Define primary and backup responders for each monitor. StatusPulse automatically rotates on-call schedules and sends reminder digests every 4 hours during active incidents.