Gaining an Overview of Event Logs

Objective

After completing this lesson, you will be able to digest different events log types.

The Event Logs Overview

Manage Event Logs application enables powerful auditability and tracking abilities. This video will help you to understand these posibilities within the Universal Model.

Step 1: Accessing Event Logs

When we go to the 'Event Logs' tile, you will see a comprehensive list of all logs. These logs capture various activities and changes within the system.

Step 2: Selecting the Environment

To narrow down the logs, you can choose the exact environment you want to pull logs for. For example, by typing the environment name here, you will filter the logs to show only events from that specific environment.

Step 3: Filtering by Log State

You can further refine the logs by choosing specific states such as 'abort', 'error', 'OK', 'warning', etc. This allows you to focus on particular types of events, making it easier to identify and troubleshoot issues.

Step 4: Exporting Logs

If needed, you can export the logs as a table. This feature is particularly useful for documentation, analysis, and reporting purposes. To do this, simply click on the export option, and you'll have a table ready for further use.

Step 5: Demonstrating the Logging Mechanism

Please note that you have a powerful mechanism for logging here, and I encourage you to maximize its use. Now, let's look at how we can use this logging feature to track changes at the data level.

Step 6: Data Level Tracing

From the data level, we can also perform tracing or logging events. For example, if I click on this entry, I can see exactly who made the change and what was changed. This is crucial for understanding the history of modifications.

Step 7: Additional Filtering

If you have thousands of logs, you can use additional filters to narrow down your search. For instance, if you want to know who created a specific item, you can use the filters to find this information quickly.

Step 8: Specific User Activity

You can also filter to see specific user activities, such as:

  • Who created this item?
  • What actions did a particular user perform? This detailed filtering helps in providing a better logging experience, not just in the event logs but also in the system's detailed view."

Step 9: Reviewing Logged Events

For example, if I look at this log, I can see that 98 pieces were counted, and then the value was edited from 400 to 500. This demonstrates the level of detail available in the logs for traceability.

Conclusion

In summary, the 'Manage Event Logs' feature in UM provides a comprehensive and detailed audit trail of all activities. This helps in ensuring accountability, security, and compliance across all modeling and processing activities.