Skip to main content

Using the Event Log

Event log functionality serves as a comprehensive record of user actions, providing a detailed history of activities that enables administrators to monitor and trace modifications and ensure accountability. By meticulously documenting every action, event logs allow for quick detection of issues, facilitating efficient troubleshooting and minimizing downtime.

The Event Log tracks activity across the platform with detailed event records containing event ID, object information, action performed, operation status, timestamp, and user attribution. User activity logging captures all user-level actions with evaluation screen access and TXT export for operational oversight. Role management logging tracks role-related actions with impacted records display and change summary export capabilities.

Organizations maintain a complete audit trail that meets compliance and governance requirements. Administrators can quickly identify who made specific changes and when those changes occurred. Technical teams can troubleshoot issues effectively using detailed operation status information. Security teams benefit from monitoring capabilities across all object types with IP address and user tracking. Management obtains a comprehensive historical record for change management processes. Event logs can be filtered by multiple criteria and exported for detailed analysis.

Access

To access the event log, in the Explore Pane, go to Governance, Monitor and click on Event Log. For detailed filtering and operation procedures, see Event Log Actions.

What the Event Log Captures

The Event Log provides comprehensive activity tracking across the platform, capturing operations performed on supported objects:

  • User Management Activities - Adding users, removing users, locking users, unlocking users.

  • Role Management Operations - Creating roles, modifying role permissions, deleting roles, assigning roles.

  • Object Operations - Operations on Dimension, Sheet, Metric, Action, Snippet, Journal, Process, Dataflow, and Remote table objects.

Event Record Structure

Each event record contains detailed information enabling comprehensive tracking:

  • Event ID - Unique identifier for each logged event.

  • Object Information - Object ID, Object Name, and Object Type identify what was affected.

  • Event sub-type and Event Type - The sub type and type of the event.

  • Parent Object - Indicates whether the parent is a Sheet or Master Data. If a data operation is performed within a sheet, the sheet name is displayed here.

  • Change Summary - Description of the specific operation (Read, Save, Publish, Import, Export, input, deletion, addition).

  • User - User ID, Email ID, and IP Address identify who performed the action.

  • Status - Indicates whether the action succeeded or failed, along with progress information.

  • Event Time and Event End Time - Precise time at which the action occurred and ended.

User Activity Logging

Detailed logging captures whenever a user performs an activity such as modifying configurations or interacting with objects.

  • Comprehensive Recording - Captures all user-level actions performed across the platform.

  • Evaluation Screen - Users can access the evaluation screen to review what changes were made and by whom, with impacted records displayed clearly.

  • TXT Export - Export a summary of user activities in TXT format for documentation or audit purposes, supporting audit, traceability, and operational oversight.

Role Management Logging

Tracking for all role-related actions provides transparency and governance around role-based access control.

  • Automatic Logging - When a user creates, modifies, or assigns a role, the system automatically logs the event.

  • Evaluation Screen Access - Logs are accessible via the evaluation screen, where users can view the impacted records.

  • Change Summary Export - Export role change summaries in TXT format, supporting audit, traceability, and access control governance.

Transparency and Accountability

  • Collaborative Environments - Maintaining a detailed record of changes through event logs keeps all users informed about modifications made to the system. This transparency is crucial for collaborative environments where multiple users may interact with the system concurrently.

  • Who, What, When - Knowing who made changes, what those changes were, and when they occurred helps in maintaining an orderly and coherent workflow.

  • Security Trail - Event logs enhance system security by providing a trail of user activities. This information is valuable for auditing purposes and helps in holding users accountable for their actions.

Filtering and Export

  • Filter Criteria - The event log can be filtered by Time Range, Event ID, Event Type, IP Address, and Updated by. Filters and selections are available to pinpoint exact changes.

  • Export for Analysis - The log can be exported for detailed analysis, enabling offline review and reporting.

  • Time-Based Filtering - Filter events by specific time periods including last 24 hours, 72 hours, or set custom time range.

Use Cases

  • Audit Trail Documentation - Export event logs to document complete audit trail for compliance requirements, tracking all user and role management activities.

  • Security Investigation - Filter event logs by IP address and user to investigate security incidents or unauthorized access attempts.

  • Change Review - Review evaluation screen to understand what changes were made to objects, by whom, and when for change management processes.

  • Troubleshooting Operations - Use operation status information in event logs to troubleshoot failed actions and identify root causes of system issues.

Was this article helpful?

We're sorry to hear that.