You can set alert actions for a site not communicating at both the system level and at a site level. 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 site level alert actions for site not communicating, see Setting 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, and the alert conditions for both Service Center Receive and Onsite Manager Processing are met, this alert is triggered.
These three alerts form a hierarchy in which the Service Center Receive and Onsite Manager Processing alerts are subsets of the Site Not Communicating alert. The two lower-level alerts can exist simultaneously. However, if two updates have been missed in addition to the conditions required to trigger the lower-level alerts, then the Site Not Communicating alert triggers. The lower-level alerts self-heal, as they are subsumed by the Site Not Communicating alert.
The following table outlines which alerts are triggered for various combinations of site communication failure conditions:
What 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. |
Service Center has not received information from Onsite Manager for 65 minutes | both the Service Center Receive and Onsite Manager Processing alerts are triggered. |
Service Center has not received information from Onsite Manager for 6 minutes and two updates have been missed. | 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. |
| 12 hours has passed since an Onsite Manager has retrieved information from Service Center and two updates have been missed. | 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. |
Service Center has not received information from Onsite Manager for 65 minutes and 12 hours has passed since an Onsite Manager has retrieved information from Service Center and two updates have been missed. | 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 Configuration > System Settings.
- Click the Alert Configuration tab.
- 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 an Alert Category. 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 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 will take effect.
- Repeat steps 1 to 5 as needed to configure the alert actions for the Service Center Receive and Onsite Manager Processing alerts.
- Click Save.
See Also