Actions are rules attached to a check that act based on check failures. When creating a new check against some service, regardless of the check type, in case of failure the user should decide what actions need to be taken. The below explains the supported actions for failed checks.


Sending an email is useful for reporting of some happened event but typically is not reacted to very fast. Mailing groups are great to get a wider recipient audience for the failing check.


Sometimes it is alright for a check to fail once, or twice, before it is necessary to start further investigation. The wait time is of the same duration as the check interval. A wait means that it is not necessary to jump on the current failure, but let’s wait for the following checks results.


Failures that require immediate attention are good to be sent as messages to a shared Slack channel. Before it is possible to send messages to Slack, the channel and permissions to send to channel need to be provided in user’s settings. Slack rights and channel information are configured under main menu’s Settings link as shown in below screenshot.

When clicking on the Slack button, it is necessary to login to Slack and give Bitbar Monitoring the right to post to the desired channel.


PagerDuty is an information gathering platform where various systems may send their notifications. PagerDuty provides means to handle the incoming events and take appropriate actions on them.

Before it is possible to send anything to PagerDuty it is necessary to set up the connection between Bitbar Monitoring service and PagerDuty. This can be done under the user settings. A screenshot of this is above.