You can set alert actions for a site not communicating at both the system level and by site. It is recommended that you first set your system-level defaults, and then override these defaults as needed on the site level. For more information about setting system-level alert actions for site not communicating, see Setting System-Wide Alerting Actions for Site Communication Failures.
Barracuda RMM includes three alerts that notify you of site communication failures:
- Service Center Receive—triggers when Service Center has not received information from an Onsite Manager for 65 minutes.
- Onsite Manager Processing—triggers when 12 hours has passed since an Onsite Manager has retrieved information, such as configuration changes, from Service Center.
- Site Not Communicating—status and asset information is sent to Service Center every two minutes. When two updates have been missed, this alert is triggered.
The Site Not Communicating alert is considered more important than the Service Center Receive and the Onsite Manager Processing alerts.
The Service Center Receive and the Onsite Manager Processing alerts are of equal importance to each other. As a result, if two updates are missed and you get a Site Not Communicating alert, you do not also get a Service Center Receive or Onsite Manager Processing alert; in that case, the Service Center Receive or Onsite Manager Processing alert self-heals.
In the case where the Service Center has not received information from an Onsite Manager for 65 minutes and 12 hours have passed since an Onsite Manager has retrieved information, both the Service Center Receive alert and the Onsite Manager Processing alert are triggered.
The following table outlines which alerts are triggered for various combinations of site communication failure conditions:
| If... | Then... |
Service Center has not received information from Onsite Manager for 65 minutes | the Service Center Receive alert is triggered. |
| 12 hours has passed since an Onsite Manager has retrieved information from Service Center | the Onsite Manager Processing alert is triggered. |
| Two updates have been missed | the Site Not Communicating alert is triggered. |
Service Center has not received information from Onsite Manager for 65 minutes | the Service Center Receive alert is triggered |
Service Center has not received information from Onsite Manager for 65 minutes | the Site Not Communicating alert is triggered. Any existing Service Center Receive and Onsite Manager Processing alerts self-heal, as the Site Not Communicating alert takes precedence. |
- In Service Center, click Site Management > Sites.
- Click the site you want to edit.
- Click the Alert Configuration tab.
- In the Site Not Communicating Alert Configuration section, clear the Use System Defaults check box.
- Click Modify.
- Do the following to change the default alert configuration:
- To add an alert category when a site is not communicating so that it appears on the Central Dashboard, click Categorize Alert and add a category from the list. To set up a new alert category, see Creating Alert Categories. Click Save.
- To create a trouble ticket when a site is not communicating, select the Create Trouble Ticket check box.
- To send an email when a site is not communicating, select the Send Email check box and configure the settings.
- To call a pager when a site is not communicating, select the Call Pager check box and click Call Pager. Select the All Users for the Site Whose Role is Configured to Receive Pager Alerts option button. Click Save.
- To escalate an alert if an alert has not been resolved in a set amount of time, select the Escalate Alert check box and select a time after which the Alert Escalation takes effect.
- Repeat steps 1 to 6 as needed to configure the alert actions for the Service Center Receive and Onsite Manager Processing alerts.
- Click Save.