Audit logs
The organization-scoped record of who changed what, how entries are shaped, and what is not available yet.
Changes to the things an organization owns, from applications and environment variables to buckets, plans and API keys, are recorded against that organization together with the actor that made them. The same change produces the same entry whether it came from the console, the CLI, or the API.
Entries are written, not yet readable
There is no audit-log page in the console, no /audit-logs API endpoint, and no SDK resource. Entries accumulate
against your organization from the moment it is created, and a read surface is the missing half. Plan around that, and
ask cs@gigadrive.de if you need an extract in the meantime.
What an entry carries
| Field | Contents |
|---|---|
organizationId | Always set. Every entry belongs to exactly one organization. |
action | <category>.<verb>, for example env_var.update. See Event reference. |
operationType | CREATE, READ, UPDATE, DELETE, or ACTION |
actorType | USER, ORGANIZATION, APPLICATION, DEPLOYMENT, or FUNCTION |
actorSource | IDP for a signed-in person, API_KEY for a machine credential, SYSTEM for platform-initiated work |
actorId, actorDisplayName, apiKeyId | Who or what acted, and which key it presented |
targetType, targetId, targetDisplayName | What was acted on, with a human-readable name captured at the time |
ipAddress, userAgent, requestId, country | Request context. country is an ISO 3166-1 alpha-2 code. |
payload | The non-sensitive fields of the change. Updates carry before and after. |
success, errorMessage, errorCode | Outcome. success defaults to true. |
createdAt | When the entry was written |
Writing never blocks the change
An audit write that fails does not fail the operation that triggered it. Losing an entry is bad; refusing a deployment because one could not be written is worse.
The same reasoning shapes what lands in payload: the fields that make a change intelligible, and never the ones that would turn the log into a secret store. An environment variable entry names the key and not the value.