LogoLogo
  • Welcome to e6data
  • Introduction to e6data
    • Concepts
    • Architecture
      • e6data in VPC Deployment Model
      • Connect to e6data serverless compute
  • Get Started
  • Sign Up
  • Setup
    • AWS Setup
      • In VPC Deployment (AWS)
        • Prerequisite Infrastructure
        • Infrastructure & Permissions for e6data
        • Setup Kubernetes Components
        • Setup using Terraform in AWS
          • Update a AWS Terraform for your Workspace
        • AWS PrivateLink and e6data
        • VPC Peering | e6data on AWS
      • Connect to e6data serverless compute (AWS)
        • Workspace Creation
        • Catalog Creation
          • Glue Metastore
          • Hive Metastore
          • Unity Catalog
        • Cluster Creation
    • GCP Setup
      • In VPC Deployment (GCP)
        • Prerequisite Infrastructure
        • Infrastructure & Permissions for e6data
        • Setup Kubernetes Components
        • Setup using Terraform in GCP
        • Update a GCP Terraform for your Workspace
      • Connect to e6data serverless compute (GCP)
    • Azure Setup
      • Prerequisite Infrastructure
      • Infrastructure & Permissions for e6data
      • Setup Kubernetes Components
      • Setup using Terraform in AZURE
        • Update a AZURE Terraform for your Workspace
  • Workspaces
    • Create Workspaces
    • Enable/Disable Workspaces
    • Update a Workspace
    • Delete a Workspace
  • Catalogs
    • Create Catalogs
      • Hive Metastore
        • Connect to a Hive Metastore
        • Edit a Hive Metastore Connection
        • Delete a Hive Metastore Connection
      • Glue Metastore
        • Connect to a Glue Metastore
        • Edit a Glue Metastore Connection
        • Delete a Glue Metastore Connection
      • Unity Catalog
        • Connect to Unity Catalog
        • Edit Unity Catalog
        • Delete Unity Catalog
      • Cross-account Catalog Access
        • Configure Cross-account Catalog to Access AWS Hive Metastore
        • Configure Cross-account Catalog to Access Unity Catalog
        • Configure Cross-account Catalog to Access AWS Glue
        • Configure Cross-account Catalog to Access GCP Hive Metastore
    • Manage Catalogs
    • Privileges
      • Access Control
      • Column Masking
      • Row Filter
  • Clusters
    • Edit & Delete Clusters
    • Suspend & Resume Clusters
    • Cluster Size
    • Load Based Sizing
    • Auto Suspension
    • Query Timeout
    • Monitoring
    • Connection Info
  • Pools
    • Delete Pools
  • Query Editor
    • Editor Pane
    • Results Pane
    • Schema Explorer
    • Data Preview
  • Notebook
    • Editor Pane
    • Results Pane
    • Schema Explorer
    • Data Preview
  • Query History
    • Query Count API
  • Connectivity
    • IP Sets
    • Endpoints
    • Cloud Resources
    • Network Firewall
  • Access Control
    • Users
    • Groups
    • Roles
      • Permissions
      • Policies
    • Single Sign-On (SSO)
      • AWS SSO
      • Okta
      • Microsoft My Apps-SSO
      • Icons for IdP
    • Service Accounts
    • Multi-Factor Authentication (Beta)
  • Usage and Cost Management
  • Audit Log
  • User Settings
    • Profile
    • Personal Access Tokens (PAT)
  • Advanced Features
    • Cross-Catalog & Cross-Schema Querying
  • Supported Data Types
  • SQL Command Reference
    • Query Syntax
      • General functions
    • Aggregate Functions
    • Mathematical Functions & Operators
      • Arithematic Operators
      • Rounding and Truncation Functions
      • Exponential and Root Functions
      • Trigonometric Functions
      • Logarithmic Functions
    • String Functions
    • Date-Time Functions
      • Constant Functions
      • Conversion Functions
      • Date Truncate Function
      • Addition and Subtraction Functions
      • Extraction Functions
      • Format Functions
      • Timezone Functions
    • Conditional Expressions
    • Conversion Functions
    • Window Functions
    • Comparison Operators & Functions
    • Logical Operators
    • Statistical Functions
    • Bitwise Functions
    • Array Functions
    • Regular Expression Functions
    • Generate Functions
    • Cardinality Estimation Functions
    • JSON Functions
    • Checksum Functions
    • Unload Function (Copy into)
    • Struct Functions
  • Equivalent Functions & Operators
  • Connectors & Drivers
    • DBeaver
    • DbVisualiser
    • Apache Superset
    • Jupyter Notebook
    • Tableau Cloud
    • Tableau Desktop
    • Power BI
    • Metabase
    • Zeppelin
    • Python Connector
      • Code Samples
    • JDBC Driver
      • Code Samples
      • API Support
    • Configure Cluster Ingress
      • ALB Ingress in Kubernetes
      • GCE Ingress in Kubernetes
      • Ingress-Nginx in Kubernetes
  • Security & Trust
    • Best Practices
      • AWS Best Practices
    • Features & Responsibilities Matrix
    • Data Protection Addendum(DPA)
  • Tutorials and Best Practices
    • How to configure HIVE metastore if you don't have one?
    • How-To Videos
  • Known Limitations
    • SQL Limitations
    • Other Limitations
    • Restart Triggers
    • Cloud Provider Limitations
  • Error Codes
    • General Errors
    • User Account Errors
    • Workspace Errors
    • Catalog Errors
    • Cluster Errors
    • Data Governance Errors
    • Query History Errors
    • Query Editor Errors
    • Pool Errors
    • Connectivity Errors
  • Terms & Condition
  • Privacy Policy
    • Cookie Policy
  • FAQs
    • Workspace Setup
    • Security
    • Catalog Privileges
  • Services Utilised for e6data Deployment
    • AWS supported regions
    • GCP supported regions
    • AZURE supported regions
  • Release Notes & Updates
    • 6th Sept 2024
    • 6th June 2024
    • 18th April 2024
    • 9th April 2024
    • 30th March 2024
    • 16th March 2024
    • 14th March 2024
    • 12th March 2024
    • 2nd March 2024
    • 10th February 2024
    • 3rd February 2024
    • 17th January 2024
    • 9th January 2024
    • 3rd January 2024
    • 18th December 2023
    • 12th December 2023
    • 9th December 2023
    • 4th December 2023
    • 27th November 2023
    • 8th September 2023
    • 4th September 2023
    • 26th August 2023
    • 21st August 2023
    • 19th July 2023
    • 23rd May 2023
    • 5th May 2023
    • 28th April 2023
    • 19th April 2023
    • 15th April 2023
    • 10th April 2023
    • 30th March 2023
Powered by GitBook
On this page
  • Accessing the Audit Log
  • Using the Audit Log
  • Filtering Logs
  • Audit log Records
  • Overview
  • Event Details
  • Scenario
  • Process
  • API Accessibility
  • Data Immutability
  • Timezone Adherence
  • Searching and Filtering Events

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.

PreviousUsage and Cost ManagementNextUser Settings

Last updated 5 months ago

Accessing the Audit Log

Who Can Access?

The Audit Log is available to:

  • Super Admin

  • Workspace Admin

Ensure you have the necessary permissions to access this feature.

Using the Audit Log

Click on the Audit logs option in the left navigation panel

Filtering Logs

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

Audit log Records

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

Overview

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 Details

  • 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: -

Scenario

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.

Process

  1. Initiation: The auto-refresh operation was initiated by an authorized user within our organization.

  2. Execution: The operation started at 10:09 AM IST and concluded at 10:10 AM IST, taking approximately 63.572 seconds to complete.

  3. 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.

API Accessibility

  • 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.

Data Immutability

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.

Timezone Adherence

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.

Searching and Filtering Events

The events in the Audit Log are indexed for searchability:

  1. Use the search bar to quickly locate specific actions or events.

  2. 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!