Guides
Advanced Monitoring Settings
Deep-dive articles for complex uptime-checking scenarios — conversion chains, API latency budgets, IP allowlisting, and more.
Browse by Category
Pick a topic area to narrow down the guides. Each article includes step-by-step instructions, configuration examples, and recommended thresholds for production use.
API & Endpoint Monitoring
Response-time budgets, status-code assertions, JSON-schema validation, and retry policies for REST and GraphQL endpoints.
View 4 guidesConversion & Funnel Tracking
Multi-step health checks that verify checkout flows, SaaS onboarding sequences, and payment gateway handshakes end to end.
View 3 guidesNetwork & Access Control
IP whitelist configuration, DNS resolution routing, TLS certificate pinning, and geo-targeted probe selection.
View 3 guidesAlerting & Escalation
Incident routing rules, Slack/PagerDuty webhooks, deduplication windows, and runbook attachment for on-call teams.
View 2 guidesAll Guides
Ten articles covering the most requested advanced configurations. Each guide was written by the Pulsely engineering team and tested against live production workloads.
API & Endpoint Monitoring
Monitoring Conversion Chains
Chain five sequential HTTP checks — landing page → product detail → cart add → checkout → confirmation — into a single funnel metric. Learn how to set per-step timeouts (800 ms each), suppress false positives with a 2-probe consensus rule, and surface the exact step that failed in your incident dashboard.
Read guideAPI & Endpoint Monitoring
Checking API Response Time
Define a p95 latency budget of 320 ms for your /v2/orders endpoint. Configure Pulsely to capture TTFB, DNS lookup, TCP handshake, and TLS negotiation separately so you can isolate whether slowdowns originate from your application server, your CDN, or your database layer.
Read guideNetwork & Access Control
Setting Up an IP Whitelist
Restrict Pulsely probe traffic to your internal load balancer by adding the 18 probe IP ranges (e.g., 198.51.100.0/24, 203.0.113.0/24) to your firewall allowlist. Includes instructions for AWS Security Groups, GCP Firewall Rules, and Cloudflare Access policies.
Read guideAPI & Endpoint Monitoring
Validating JSON Response Bodies
Use Pulsely's JSON assertion engine to verify that your /health endpoint returns {"status":"ok"} with a numeric "latency_ms" field under 150. Catch silent regressions where your API returns 200 OK but serves stale or malformed data.
Read guideAPI & Endpoint Monitoring
Configuring Retry Policies for Flaky Endpoints
Set a 3-attempt retry with exponential backoff (1 s → 2 s → 4 s) for endpoints that occasionally return 503 during deployments. Learn how retries interact with your overall downtime window and why you should cap retries at three to avoid masking real outages.
Read guideConversion & Funnel Tracking
End-to-End Checkout Flow Verification
Automate a full purchase simulation using Pulsely's multi-step checker: add a test SKU to cart, apply a promo code, select Stripe as payment method, and verify the confirmation email arrives at test@pulsely-checks.io within 12 seconds.
Read guideConversion & Funnel Tracking
SaaS Onboarding Sequence Health Check
Monitor the seven-step signup flow — invite email → registration form → payment page → webhook to Stripe → account provisioning → welcome email → first dashboard load — and receive a single composite uptime percentage for your entire onboarding pipeline.
Read guideNetwork & Access Control
Geo-Targeted Probe Selection
Assign specific probe locations (Frankfurt, São Paulo, Singapore, Ashburn) to checks based on where your users are concentrated. Compare latency and availability across regions and set region-specific alert thresholds so a brief EU blip doesn't page your APAC on-call engineer.
Read guideNetwork & Access Control
TLS Certificate Pinning & Expiry Alerts
Pin your expected certificate subject and issuer (e.g., CN=*.example.com, Issuer=DigiCert Global G2) and configure alerts that fire 30, 14, and 3 days before expiry. Prevent the infamous Let's Encrypt silent-renewal failure from taking your site offline.
Read guideAlerting & Escalation
Incident Routing & Deduplication
Route critical API failures to PagerDuty with a 5-minute dedup window, send non-critical DNS warnings to a dedicated #monitoring-slack channel, and attach your runbook URL to every alert payload so responders never guess which playbook to follow.
Read guide