When a check fails it’s important to notify the right people to investigate whether an issue is affecting availability or performance.
For Real Browser, Uptime, and API checks you can set up notification settings on the 'Notifications' tab:
- Select users or groups to notify
- Define how many times the check needs to fail before triggering an alert notification
- Specify how to notify the user or group - via email, phone, or text message
- If you want to notify a user or group that isn’t available in the dropdown, you can create new users and groups under Admin > Users and Groups
- As a best practice, it's recommended to only notify users after 2 or more consecutive errors
- Optional You can set specific hours for notifications (i.e. If you only want to notify during business hours or when a specific user is on shift)
- Rigor’s alerts are based on a change of state (e.g. failed vs. back online), so the escalation alerts trigger based on the initial alert.
- By design, Rigor does not alert on every failure, since it would create a lot of noise in one’s inbox and subsequently become ignored or take time away from those working to resolve a known issue that Rigor has identified.
Respond to Alerts
When you receive alerts from Rigor you can review the status and details of the check alert. You can click on the Alert Information link in your notification, which will take you to the alert in Rigor where you can acknowledge it. Taking ownership of an alert and acknowledging that it’s under review will prevent any escalation alerts from sending.