Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Mobility platform activity monitoring

Mobility administrators can monitor activities within the Mobility server cluster. The BMC Mobility Administration console has a configuration tab dedicated to activity monitoring. Both Mobility administrators and Mobility tenant administrators can enable activity monitoring, and they can specify what data is captured. 

Mobility audit configurations
User Activity Auditing Config.png

If you select the Operation check box is selected, the server logs the API call name, the API call status (succeeded or not), and the duration of the API call. If you select the Application check box, the name of the mobile application is recorded in the audit form. In addition, if the operation is an EntryAssembler API call, the data source name is recorded with the application name. For example, Incidents, StatusReason means that the operation is for the Incident Management application on the StatusReason data source.

The activity data is captured in the Mobility Usage Auditing form. That form has low-level security enabled. Therefore, each tenant administrator can see only activities happening in their own tenant group. Mobility administrators can see activities of the entire mobility cluster. The following figure shows the form:

Mobility Usage Auditing form
AuditForm.png

This usage auditing form can fill up quickly, especially when the mobility cluster is under heavy load. Therefore, an escalation called Mobility Administration: CleanupUsageAuditingData cleans up audit data every three days. By default, this escalation is disabled. Mobility administrators can enable the escalation and customize it for their environment.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*