Trails is your organization’s audit log. Each change made through an EZGH Cloud public API in
your organization, and each change the platform makes to your resources, is recorded as an event:
who acted, from where, with which credential, on which resources, and whether it succeeded.
You can browse and filter events in the console, look them up with the API or the ezgh CLI,
and run SQL over them with Trails Query.
Event format
Every field of a Trails event, with an example.
Look up events
Filter events in the console, the CLI and the API.
Trails Query
Run SQL over your events, asynchronously.
Deliver to Observability
Deliver your events, as they happen, into a project's Observability as logs.
What Trails records
Events come from these event sources:
| Event source | Activity |
|---|---|
organizations.ezghcloud.com |
Organizations and projects |
iam.ezghcloud.com |
Users, groups, bots, policies, API keys, invitations, SSO and SCIM settings |
signin.ezghcloud.com |
Sign-in, sign-out and account operations |
billing.ezghcloud.com |
Billing details, payment methods, invoices and costs |
obs.ezghcloud.com |
Observability datasets, dashboards, services and async queries |
domains.ezghcloud.com |
Registering and renewing domains, and changing their settings, nameservers, DNSSEC and registrant contacts |
files.ezghcloud.com |
Creating, changing and deleting file systems, mount targets and access points |
git.ezghcloud.com |
Creating, changing and deleting repositories and branch rules, pushes, pull requests, reviews, merges and checks |
kubernetes.ezghcloud.com |
Creating, changing and deleting clusters, node groups, add-ons, access entries and pod identity associations, and signing in to clusters |
databases.ezghcloud.com |
Creating, changing, failing over and deleting databases, their backups and blue/green deployments |
sandboxes.ezghcloud.com |
Creating, suspending, resuming, stopping, starting and deleting sandboxes, and refused commands and file calls |
caches.ezghcloud.com |
Creating, changing, failing over, flushing and deleting caches, their users and blue/green deployments |
warehouse.ezghcloud.com |
Creating, changing and deleting warehouses, their users, databases and connections, rotating users’ passwords, on-demand backups, query editor queries and port forwards |
hostedqueues.ezghcloud.com |
Creating, changing, upgrading and deleting clusters and their users, Kafka topics and consumer groups, and RabbitMQ vhosts, queues, exchanges, bindings and policies |
compute.ezghcloud.com |
Launching, starting, stopping, rebooting, resizing, changing and terminating instances, attaching volumes and network interfaces, console sessions, SSH keys and autoscaling groups |
lb.ezghcloud.com |
Creating, changing and deleting load balancers, listeners and target groups, and registering and deregistering targets |
waf.ezghcloud.com |
Creating, changing and deleting WAFs, and attaching them to and detaching them from load balancers |
cdn.ezghcloud.com |
Creating, changing and deleting distributions |
trails.ezghcloud.com |
Starting and cancelling Trails queries, and creating, changing and deleting deliveries |
| Activity | Recorded |
|---|---|
| A call that changes something, whether it succeeds or fails | Yes (readOnly: false) |
A call that only reads, such as GetProject or LookupEvents |
No, except reading a secret’s value (readOnly: true) |
A change refused because the caller lacks permission (403 access_denied) |
Yes, with errorCode |
A change that returns a 400 error to a member of the organization |
Yes, with errorCode |
| A change the platform makes to your resources on its own | Yes (eventType: ServiceEvent) |
| An EZGH product reading a secret through a grant | Yes (ResolveSecret, readOnly: true) |
A request without valid credentials (401) |
No |
A request for an organization the caller doesn’t belong to (404) |
No |
| A write from a browser session refused by the Origin check | No |
Trails records changes, not reads: reads are most API calls, and changes are what an audit log is
for. The exceptions are reads of secret values, which Trails keeps so you can see who saw a
secret: AccessSecretVersion and AccessSecretField from your own calls, and ResolveSecret
when a product reads one through a grant. Events recorded before October 2026 include other reads.
An event is recorded only once the caller is known to be a member of the organization. Requests that no one can be held to, and probes of organizations you don’t belong to, don’t appear in anyone’s Trails.
Trails never records passwords, tokens, cookies, client secrets or payment details. Request
fields that could hold a secret are replaced with HIDDEN_DUE_TO_SECURITY_REASONS. For document
processing, Trails records the page count, size and file type, never the document’s content,
file name or extracted text.
Retention
Trails keeps events for 30 days, then deletes them. Trails Query results are kept for 7 days after the query finishes. To keep events longer, deliver them to Observability, where they’re kept for the dataset’s log retention.
Who can use Trails
Trails is organization-wide. Access is controlled by these IAM actions:
| Action | Allows | In AdministratorAccess and TrailsFullAccess |
In ReadOnlyAccess |
|---|---|---|---|
audit.events.list |
Look up events and read single events | Yes | Yes |
audit.queries.run |
Start Trails queries, and read the query schema | Yes | Yes |
audit.queries.get |
See your own queries’ status and results | Yes | Yes |
audit.queries.list |
See everyone’s queries and their results | Yes | Yes |
audit.queries.cancel |
Cancel queries you can see | Yes | No |
audit.deliveries.list, audit.deliveries.get |
List and view deliveries | Yes | Yes |
audit.deliveries.create, .update, .delete |
Create, change and delete deliveries | Yes | No |
The root user can do all of these. API keys act with their owner’s access. See IAM for policies.