Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Enterprise Mobility Server 3.8
  3. Monitoring and reporting
  4. Monitoring probes and tools
  5. Java Management Extensions (JMX)-compliant monitoring tools
  6. Monitoring attributes

Monitoring attributes

The following table describes the statistics that you can use to monitor the health of 
BEMS
 server, users, and 
BEMS-Docs
 using the monitoring tool. 
Statistic
Description
Push Notifications
 
RelayStats
<
notification type
>RelayStats
This attribute specifies the number of push notifications for each push notification type (for example, APNS, GNP, and 
FCM
). If this number stops rising, then 
BEMS
 is not sending any push notifications.
The numbers should increase over short intervals. 
EWSStats 
EWSConnectedUserCount
This attribute specifies the number of users on the 
Microsoft Exchange Web Services
 instance that 
BEMS
 uses to connect to the 
Microsoft Exchange Server
 so that it can monitor the users' mailboxes. This attribute reflects the number of users most likely to be receiving push notifications unless 
BEMS
 is experiencing errors with its 
Microsoft Exchange Web Services
 connections to the 
Microsoft Exchange Server
.
The EWSConnectedUserCount should be equal across all 
Microsoft Exchange Web Services
 instances in a cluster. If this count drops to 0, then the 
Microsoft Exchange Web Services
 instance is not servicing any user mailboxes.
UserStats
UsersCount
This attribute specifies the total number of users across the 
BEMS
 cluster which successfully registered a device and are successfully autodiscovered by 
BEMS
. The UsersCount does not reflect the number of devices receiving push notifications.
StaleUsersCount
This attribute specifies the total number of users across the 
BEMS
 cluster that 
BEMS
 is no longer sending push notifications to because the devices that were registered previously haven't registered in the past 72 hours.
HealthStats
HealthStats
This attribute specifies the overall health of the 
BEMS
 status, including health of consumer threads, producer threads, ActiveMQ, and access to the database.
ClientAPIStats
ClientAPIStats
This attribute identifies generic problems with the 
BEMS
 service by monitoring the average and maximum processing time of requests to the 
BEMS
 database. This statistic is for the last minute only. For example, if the LookupUser is {Min:10, Max:90000, Average:50000, Count:26}, it means that 
BEMS
 received 26 LookupUser requests in the last minute and the average duration is 50,000 milliseconds.
DatabaseStats
DatabaseStats
This attribute can identify common failure points for the 
BEMS
 Infrastructure. This attribute monitors statistics such as the average, maximum, minimum, and number of requests to 
BEMS
 if the NumOfRequests is 25, it means 
BEMS
 received 25 database requests in the last minute. If the database stops, the processing time displays 
Infinity
.
 AutodiscoverStats
EAS
This attribute specifies the total number of successful or failed Active Directory requests for EAS client requests.  
EWS
This attribute specifies the total number of successful or failed Active Directory requests for all EWS requests and client requests.   
Tests
This attribute specifies the total number of successful or failed Active Directory requests for both EWS and EAS tests. 
BEMS-Docs
DocsConfigInfo
This attribute specifies the overall 
BEMS-Docs
 configuration information, including the version of BEMS that is installed, the status of all bundles, and database status.
DocsServices
This attribute specifies overall health of the 
BEMS-Docs
 service, including the total number of requests, downloads, and uploads with the average processing time. The success and failure of the statistics are also included.
DocsStorageProviders
This attribute specifies the total number of requests and downloads to a specific fileshare (for example, 
Microsoft SharePoint
, 
Microsoft SharePoint Online
, CMIS, and 
Box
).