SITEPULSE / INFORMATION & CAPABILITIES
Your website is up. Keep an eye on it.
Follow availability over time instead of relying on one successful check.
Der vollständige Text unten ist auf Englisch.
A CLOSER LOOK
How individual checks become a history.
Scheduled checks collect responses over time. Repeated failures trigger a notification when monitoring and notifications are enabled.
- 01ScheduleScheduled task
- 02HTTP responseStatus and timing
- 03HistoryA series of checks
- 04NotificationAfter 3 failures
From a single test to a history
With monitoring enabled, the platform periodically records status, HTTP code, response time and available SSL metrics. History helps reveal recurring problems and distinguish a momentary slowdown from a sustained interruption.
Activation and intervals
Add a website from your workspace and enable monitoring when your plan permits it. Checks depend on scheduled server tasks running. An interval means a planned series of checks rather than continuous real-time observation.
Failures and recovery
A first failure creates an initial incident record. A downtime notification triggers after three consecutive failures when notifications are enabled. Recovery closes the incident. In the current implementation, notifications go to the platform’s configured contact.
What the results mean
A successful HTTP response does not prove that every website function works. Monitoring does not automatically test checkout, registration or user journeys. Combine it with application tests and your own infrastructure monitoring.