Audit Log
Audit Log feature of e6data , will help you navigate and utilise the Audit Logs effectively to track administrative actions related to workspaces, catalogs, and clusters.
Last updated
Audit Log feature of e6data , will help you navigate and utilise the Audit Logs effectively to track administrative actions related to workspaces, catalogs, and clusters.
Last updated
Who Can Access?
The Audit Log is available to:
Super Admin
Workspace Admin
Ensure you have the necessary permissions to access this feature.
Click on the Audit logs option in the left navigation panel
You can customize your view of the audit logs with the following filters:
Date: Select a specific date range.
User: Filter by the user who performed the action.
Operation Type: Choose specific actions (e.g., create, update, delete, enable, disable, auto refresh etc).
Component: Filter by the type of component (e.g., workspace, cluster, catalog). The logs will display in a clear table format for easy browsing
Component Name: Filter by component name which provides a specific designation for the component involved
Each record in the Audit logs tab includes the following columns:
Event ID: The Event ID is a unique identifier assigned to a specific event in the system.
Time stamp: The Timestamp column records the exact date and time when the event occurred, providing a precise reference for when actions were initiated and completed. This is crucial for tracking the sequence of events and ensuring accurate auditing.
Component:The Component refers to the specific part of the system involved in the event. It can be workspace , cluster and catalog
Component Name:The Component Name provides a more specific designation for the component involved. Typically would identify which specific component was affected during the operation.
Operation:The Operation describes what action was performed during the event. It can be update, create , delete, auto refresh disable , enable etc
User:The User field identifies who initiated or was responsible for the action recorded in the event log.
Note : In UI we also display the total events for the selected parameters along with the successful and failure event for that time range
Example Demonstration of the Audit Log Feature
This example illustrates the functionality of our Audit Log feature by showcasing a successful auto-refresh operation on a component within our catalog system. This demonstration highlights how the Audit Log tracks and records important events, providing transparency and accountability.
Event ID: m38h76c198f8-plt-beta-sjdvvg9m
Start Time: 08 Nov 2024 13:59:34 IST
End Time: 08 Nov 2024 13:59:35 IST
Component: Catalog
Component Name: [Redacted for Privacy]
Operation: Delete
Status: Success
Duration: 1.204 s
User: [Redacted for Privacy]
Changes: -
On November 08, 2024, our Audit Log captured an delete operation executed on a specific component in the catalog system. This event is an excellent example of how the Audit Log provides a detailed record of administrative actions.
Initiation: The auto-refresh operation was initiated by an authorized user within our organization.
Execution: The operation started at 10:09 AM IST and concluded at 10:10 AM IST, taking approximately 63.572 seconds to complete.
Outcome: The operation was recorded as successful, with no changes made during this refresh cycle.
This demonstration exemplifies how the Audit Log feature tracks key events such as auto-refresh operations. It ensures that all actions are logged with critical details, allowing users to review and audit activities within the system effectively.
For developers and advanced users, the Audit Log feature will be accessible via our API in an upcoming release. This enhancement will allow you to integrate audit log functionalities into your applications and enable programmatic access to audit data, providing greater flexibility and control over your auditing processes.
Please note that all audit log entries are immutable. Once an entry is created, it cannot be altered or deleted. This ensures that historical records remain intact and trustworthy.
Timestamps in the audit log automatically adjust for timezone changes. This guarantees that all logged actions are accurately represented according to the time zone in which they were performed.
The events in the Audit Log are indexed for searchability:
Use the search bar to quickly locate specific actions or events.
Apply additional filters as needed to refine your search results.
This feature helps streamline the process of auditing administrative activities.
E6data maintains audit logs for all components, including those that have been deleted, for a period of up to one year (365 days). This ensures comprehensive tracking and accountability of all actions performed within the system, facilitating compliance and forensic analysis as needed.
The Audit Log feature is a powerful tool for monitoring and reviewing administrative actions within e6data's SQL engine. By utilising filtering options, download capabilities, and robust API access, you can maintain a high level of transparency and accountability in your environment.For further assistance or questions regarding the Audit Log feature, please reach out to our support team or consult our knowledge base. Happy auditing!
