To detect anomalies and troubleshoot issues, you review activities such as failed logins and changes made to records and fields in your Oomnitza instance.
The role permissions for activities must be be set to read.
By default, activities are tracked for the current day and previous six days. The data retention period for activity entries is one year.
To review activities, you create filters.
You want answers to questions such as:
- When an activity was completed?
- Who completed the activity?
- How did they complete the activity?
- What type of activity was completed?
- What was the target of the activity such as asset or desktop software records or fields?
The default activities filter is set to track the activities of the user who has logged in to their Oomnitza instance and the date filter range is set to track today’s activities and the activities that occurred over the last six days. By default, the login activities of the user who has logged in are tracked and the asset records that the user created.
Track asset record activities
Let's say you want to track activities for asset records. In this scenario, you leave the users' filter blank because you want to display all activities regardless who completed the activity.
Figure: Illustration of an activities filter for asset records and fields
When you select Fields as a target, changes to any field, such as a change to a field in an asset, contract, or SaaS record is retrieved by the activities filter.
Track login activities
To track logins for all users, you leave the users' filter blank.
Activity entries
Each activity entry provides you with the following information:
- The date and time the activity was completed.
- The user or system user who completed the action. You can click the entry to open the user's record.
- The type of activity that was completed such as creating, deleting, or exporting records to spreadsheets.
- The target of the activity such as assets, or SaaS applications, or contracts. Depending on the activity type and target, you are provided with a link to the field or record that was changed. If you bulk edit records, you get a separate activity entry for each record with a link to the record that is changed.
- The source of the activity such as the Oomnitza UI, API, or an integration.
Examples of activity entries
Figure: Mockup of activity entry for changes to asset records
You can click the username to open the user's record. If the target is an object, such as assets or users, you can open the record that was changed.
Figure: Mockup of activity entry for changes to fields
If the target is a field, you can open the field that was changed.
Comments
0 comments
Please sign in to leave a comment.