eG Monitoring
 

Measures reported by XMDeviceActionsTest

Administrators can configure automated actions on the Device Manager, using which the device manager can perform actions based on user or device properties, events, or the existence of applications on devices.

For example, you can configure the following Automated Actions:

  • You can automatically notify users whose iOS or Android devices is jailbroken or rooted that they are in violation of company policy and that the device will be selectively wiped if the device is not brought into compliance.

  • You can automatically enforce a geo-fencing policy whereby if a user's device leaves a defined geographical perimeter, the device is blocked from accessing your organization's email, is selectively wiped, or is revoked.

  • You can alert users automatically when mobile devices are roaming domestically or internationally and that they may be charged extra for the service.

  • You can wipe a user's device automatically when the user leaves the company, and can disable the user's Active Directory account, so that the user can no longer access your organization's data.

  • You can place a user's device into an Out Of Compliance state automatically if the user installs a blacklisted app, and you can send the user a notification informing them that they have broken the organization's mobile app policy.

To understand the workload imposed by these actions on XenMobile, measure the efficiency of XenMobile in performing these actions, and proactively isolate bottlenecks in the execution of these actions, administrators should use the XMDeviceActionsTest test.

This test tracks the automated actions triggered on the XenMobile server, reports the number of devices on which each action was completed and the number of devices on which each action failed. In addition, this test points you to the number of devices on which each action was still pending thus leading you to figure out the probable bottlenecks in the execution of the actions.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
completed Indicates the number of devices on which this action was completed. Number The detailed diagnosis of this measure if enabled, lists the devices on which the action was completed.
pending Indicates the number of devices on which this action was still pending. Number A steady increase in the value of this measure could indicate that the server is taking too long to process the requests that are sent to perform each action.

The detailed diagnosis of this measure if enabled, lists the devices on which the action was still pending.
failed Indicates the number of devices on which this action failed to materialize. Number The detailed diagnosis of this measure if enabled, lists the devices on which the action failed to materialize.