Frequently Asked Questions
Enterprise-grade uptime for distributed systems
Support Portal v4.1.2 | Updated December 2024
General Inquiries
Platform & Account Management
Core capabilities, onboarding workflows, and multi-region validation.
How does SentinelPulse validate multi-region health checks?

Our distributed probe network operates across 14 edge locations including Frankfurt (fr-1), Tokyo (tk-2), and Virginia (us-east-1). Each endpoint is pinged every 30 seconds. A service is marked degraded only if at least three independent probes report timeout or HTTP 5xx responses within a 90-second sliding window.

Can I export historical uptime reports for compliance audits?

Yes. Navigate to Dashboard > Analytics > Export. You can generate SOC 2 and ISO 27001-aligned CSV or PDF reports covering up to 36 months of historical data. API users can also pull raw JSON payloads via the /v1/reports endpoint with standard bearer token authentication.

Billing
Plans, Cycles & Capacity
Transparent pricing structures, cycle management, and subscription adjustments.
When does my billing cycle reset and how are overages calculated?

Billing cycles anchor to your original signup date and reset monthly on that calendar day. For example, if you provisioned on November 14, your next invoice generates on December 14 at 00:00 UTC. Overages beyond your plan's monitor allowance are billed at $0.15 per additional endpoint per day, prorated to the second. You will receive automated Slack and email alerts at 80%, 90%, and 100% capacity thresholds.

What happens if I exceed my monitor limit?

SentinelPulse never disables existing monitors without explicit consent. If you hit your plan's ceiling, new monitor creation returns a 402 Payment Required error, while active checks continue uninterrupted. You can upgrade your tier instantly via the Billing dashboard or contact accounts@sentinelpulse.io to request a temporary 14-day capacity extension for staging migrations.

Technical
Operations & Data Policies
False positive mitigation, alert routing, and data retention standards.
How does SentinelPulse handle false positive alerts?

We employ a consensus-based alerting engine to eliminate single-probe noise. False positives are filtered through three layers: TLS certificate validation, HTTP status code whitelisting, and geographic probe majority voting. You can also configure custom validation payloads using our JSON matcher syntax:

{"status": 200, "body_contains": "heartbeat:ok", "timeout_ms": 4500}

Teams using PagerDuty or Opsgenie integrations can enable the "Confirmed Only" routing rule to suppress unverified incidents.

What is the data retention policy for logs and metrics?

Raw probe logs and DNS resolution traces are retained for 30 days on Standard plans and 90 days on Enterprise tiers. Aggregated uptime metrics, SLA calculations, and incident timelines are stored indefinitely in our cold storage archive. You can request permanent deletion of specific datasets via the Data Governance portal, which complies with GDPR Article 17 and CCPA opt-out requirements. Exported snapshots remain under your control indefinitely.