Review preconfigured health monitors
Your
BlackBerry Alert
system includes a set of default health monitors that are grouped into the sections described below. When you create a new monitor, you can opt to add it to one of the groups or create a new group and give it any name you want.Global monitors can be viewed from both the Global System Health and System Health links. However, organization monitors can be viewed only from the Organization view. In addition, monitors can be edited only through the Global System or organization under which they were created.
The following sections provide brief descriptions of the different kinds of health monitors available in
BlackBerry Alert
.Database
The following monitors are available in the Database section:
- Database Full Backup: This monitor runs a database query to identify the time of the most recent database full backup.
- Database Space: This monitor runs a database query to identify how much space is available in the database and throws an error if the TempDB size falls below the threshold that you specify.
- TempDB Size: This monitor identifies the minimum Microsoft TempDB data sizes required byBlackBerry Alert. The following sizes are recommended:
- 1 GB for Microsoft SQL Express edition
- 2 GB for Microsoft SQL Standard edition
- 4 GB for Microsoft SQL Enterprise edition
Web applications
The following monitors are available in the Web Applications section:
- Bing GIS: This monitor tests the Bing GIS URL for responsiveness. You can edit this setting through the Global System Health screen.
- Desktop Client Server Interface: This monitor tests the Desktop Client Server Interface URL for responsiveness.
- Management System Console: This monitor tests the Management System URL for responsiveness.
- OEM: This monitor tests the OEM URL for responsiveness.
Services
The following monitors are available in the Services section:
- IIS Longevity: This monitor tests how well the Web Application is operating by evaluating theBlackBerry Alertdiagnostic logs.
- Scheduled Job Queue: This monitor tests how well the Scheduled Job Queue is operating by running a query on the database.
- System Tasks: This monitor tests how well the system task are functioning by running a query on the database.
- Tracking & Reporting: This monitor tests how well the Tracking & Reporting system is operating by running a query on the database.
Delivery gateways
The following monitors can be in the Delivery Gateway section:
- Alert Cloud Delivery Service (East): This monitor tests the connectivity of the Alert cloud delivery service.
- Alert Cloud Delivery Service (West): This monitor tests the connectivity of the Alert cloud delivery service.
- Alert Mobile Service: This monitor tests the connectivity between the current organization and the Alert Mobile Service.
- OEM Cloud Delivery Service (East): This monitor tests the connectivity of the OEM cloud delivery service.
- OEM Cloud Delivery Service (West): This monitor tests the connectivity of the OEM cloud delivery service.
General
The following monitors are in the General section:
- CAP Events Process: This monitor checks the CAP events processor to see if it is correctly processing CAP events.
- CAP Polling Agent: This monitor checks the CAP Polling agent to see if data is being correctly added to the database.
- Database Tables - Identity Seed Max Limit: This monitor checks the identity seed values across tables to determine if they are within the safe limit.
- Desktop Notifier Load Balancing: Monitors the Desktop App incoming traffic across two or more application servers. Warnings are provided when the load is not balanced evenly across all servers.
- Online Users: This monitor identifies the number of Online Users using desktop popup alerts within the past 24 hours.
- IIM: This monitor checks the status of connectivity between theBlackBerry Alertsystem and IIM.
Alert publishing
The following monitor is available in the Alert Publishing section.
- Delivery: This monitor checks delivery batches for the alert publishing cycle and report if there have been publishing errors within the last 24–48 hours.
- Publishing: This monitor checks live publishing activity, and reports if alerts do not go live within a specified amount of time.