How to Test your Monitored Service
When you enable "Statuspal monitoring" in a service, we'll notify the recipients you select, and if enabled, automatically create and resolve an incident whenever your service goes down.
It's common that you'd want to test that this is working as advertised; a common approach users take is to configure a URL that's already down (returning a status like 5xx, 4xx, or timeout). In this case, notification recipients won't be notified and no auto-incident will be created, as the URL was down from the start.
Another approach users take is to start with a URL that's up (returning 2xx status), and then update the "Ping URL" to another URL that's down. This will also not work, as every time you update the "Ping URL" the check state gets reset.
The right way to test your monitor
In order to properly test your monitor, you'll need to set the "Ping URL" once, it should start as UP (returning 2xx status), and it should later go DOWN (returning a status like 5xx, 4xx, or timeout).
This can be easily achieved with a tool like https://webhook.site/. Just follow these steps:
1) Visit webhook.site in one tab, and keep Statuspal in another tab. Copy "Your unique URL" from webhook.site and paste it into your Statuspal service's "Ping URL".
This URL will be returning 200 status, to begin with.
2) Wait until your Statuspal's service status indicator turns green.
3) Go back to your webhook.site tab, click on Edit, change the status to 500, and click on Save.
4) Back in your Statuspal tab, wait for 5 minutes, and you should see the auto-incident created, and your notification recipients get an email notification.
If you face any issues don't hesitate to contact us at firstname.lastname@example.org.
You don't have a Status Page yet? go ahead and create one in seconds at Statuspal.io