User Actions Dashboard
The User Actions dashboard contains data about user events (that is, who did what and exactly when).
In addition to the numerous panels that can be created for the User Actions Dashboard, this dashboard contains an Audit Trail Log (for details refer to the Audit Trail Log table below. A user's activity is logged for 31 days in the Audit Trail Log panel. After 31 days the activity in the Audit Trail Log is deleted.
User Actions records can contain data associated with one or more of the following fields:
| Field | Type |
|---|---|
| id | keyword |
| requestID | keyword |
| @timestamp | date |
| userName | keyword |
| @endtime | date |
| duration | integer |
| action | keyword |
| actionDetails | keyword |
| objectType | keyword |
| objectSubtype | keyword |
| objectName | keyword |
| objectID | integer |
| apicall | boolean |
| successful | boolean |
| errorMessage | text |
| details | text |
| endPoint | text |
| changeSet | object |
Audit Trail Log Fields
| Field | Type | Description |
|---|---|---|
| @endtime | date | The date and time when the action was executed and completed. |
| @timestamp | date | The date and time at which the action started (for example, the time at which the request arrived in the system). |
| _id | ||
| _index | ||
| _type | ||
| action | keyword | EDIT | DELETE | ALTER | LOGIN | LOGOUT | EXECUTE | SEARCH | READ | TEST
|
| actionDetails | keyword | EXPORT | ADD ENTRY | ADD BATCH | PURGE | DELETE ENTRY | DELETE BATCH | LOGOUT MANUAL | LOGOUT AUTOMATIC | START | STOP | PAUSE | PRELOAD |
| apicall | boolean | Enables you to see if a change was manually performed by a user or automatically by the system. For example, if the change was manually performed by a user the apiCall is false and if the change was automatically made from a 3rd party system or external system using an API call to run the command remotely the apiCall is true. |
| details | text | Contains an additional text description of the action. |
| duration | integer | Indicates the actions duration (that is, @endtime - @timestamp) in milliseconds. |
| endPoint | uri | Indicates the API end point. |
| errorMessage | text | Contains a relevant error message (as displayed in the UI or as returned in the API response) when the request execution is not successful. |
| id | text | Contains the unique identifier. |
| objectID | integer | Contains the DBID of the object as stored in CME. |
| objectName | text | Contains the name of the object as stored in CME. |
| objectSubtype | text | Location Rule | Filtering rule | Selection Rule Contact | Upload Rule Contact |
For details, refer to the Object Types and Related Sub-types section |
| objectType | text | Contact List | Suppression List | Time Zones Map| Compliance Rule | List Rule | List Automation |
For details, refer to the Object Types and Related Sub-types section |
| requestID | keyword | Contains the Request ID. The Request ID can also be provided via the x-request-id header in the API CX Contact request. The Request ID must be generated by the client and can be used to track specific API requests (for example, for customer scripting troubleshooting purposes). |
| successful | boolean | Indicates true or false. True if the action is completed successfully and false if the action is not completed successfully. |
| userName | text | Indicates the Login Username associated with the user who initiated the action that is being logged. |
Object Types and Related Sub-types
| Object Type | Object Sub-types |
|---|---|
| Campaign Group |
|
| Campaign Template |
|
| Dialing Profile |
|
| Session Profile |
|
| Contact List |
|
| Suppression List |
|
| Time Zones Map | |
| Compliance Rule |
|
| List Rule |
|
| List Automation |
|
| Label | |
| Specification File | |
| Data Mapping |
|
| Settings |
|
| Analytics |
|
Related Topics
Comments or questions about this documentation? Contact us for support!