Overview
For security, compliance, and troubleshooting purposes, Etlworks records all important system events in the Audit Trail.
Audit entries provide visibility into actions such as running flows, editing connections, adding users, changing configurations, and more.
Admin users can view Audit Trail events for their tenant.
-
In multi-tenant environments:
Super Admins can see all events across all tenants.
Tenant Admins can only see events related to their own tenant.
The Audit Trail preserves a complete history of system activity and allows both high-level monitoring and deep-dive analysis.
Accessing the Audit Trail
To query, filter, and view events:
1. Open the Audit Trail window from the left navigation.
2. Use filters to narrow down results.
Event Details
Each event includes:
Date – Timestamp of the event (in your browser’s timezone).
Method – The operation type (e.g., runFlow, editConnection, addFlow).
User – The user who performed the action.
- Tenant - The tenant under which the event occurred. This columns is displayed only under main (non-tenant) account.
Result – Outcome (Success or Error).
Duration – How long the operation took.
Client IP / Host IP – Network details of the client and host.
View Payload
Click the link in the Method column to open the full JSON payload for the event.
The payload includes detailed metadata such as IDs, log UUIDs, flow names, event types, and other execution details, and is useful for deep-dive analysis and troubleshooting.
Open Related Object
Click the external link icon in the Method column to open the item associated with the event, such as a Flow, Flow run, or Connection.
This allows you to quickly navigate from the audit entry directly to the relevant object for further inspection or troubleshooting.
View Error Details
Click the Error link in the Result column to open the full exception stack trace.
This provides detailed information about failures, helping identify the root cause and troubleshoot issues more effectively.
Filtering Events
Etlworks provides both quick client-side filters and server-side advanced filters:
Quick search (client-side): Enter text in the search box to instantly filter visible records by values in the grid. This is lightweight and works on already loaded results.
Advanced filters (server-side): Use the filter fields to query the database. This is more and allows filtering by multiple attributes (date, time, user, status, etc.).
Available Filters
Date and Time Filters
You can narrow audit trail results using From date / To date and From time / To time filters. These filters work independently but can also be combined.
From date: Show audit records starting from 00:00 (midnight) of the selected date, in UTC timezone.
-
To date: Show audit records until the end of the selected date (23:59:59), in UTC timezone.
Together, these define a calendar date range in UTC.
From time: Show audit records at and after the specified time of day, in UTC timezone.
-
To time: Show audit records before the specified time of day, in UTC timezone.
If multiple days are included, time filters apply to each day individually. For example, setting “From time = 2:00 PM” shows only events that occurred at or after 2:00 PM on every selected day. Time filters work independently from date filters.
Other Filters
Status: Filter by execution status (e.g., Success, Error).
Method: Filter by event type (e.g., runFlow, addFlow, editConnection).
-
Parameters: Search inside event-specific payloads (see the Method column and JSON view).
Examples: search by flowName, flowId, or custom execution parameters.
Exception: Filter by part of the exception message (for failed events).
User: Show only events triggered by a specific user.
Duration more than (ms): Show only events that ran longer than the given duration in milliseconds.
Client IP: Show only events originating from a specific IP address.
Summary
The Audit Trail is an essential tool for:
Security – track who did what, and when.
Compliance – preserve a permanent log of activities across tenants.
Troubleshooting – drill down into failed events and inspect full JSON payloads.
Monitoring – quickly filter and review system usage.