Understand STACKIT Audit Log
Last updated on
The STACKIT Audit Log is a centralized service that records administrative and access events across your cloud products. Use these logs for compliance and security monitoring to track infrastructure changes. The system records actions from users, service accounts, and the STACKIT platform for services integrated with the STACKIT Audit Log. This helps you answer these key questions:
- What happened? (Event name)
- When did it happen? (Timestamp)
- Who started it? (Initiator)
- Where did it occur? (Target organization or project)
Key features
Section titled “Key features”The audit log offers these features:
- Default visibility: Admin activities are recorded by default. You do not need to set this up manually. See Retrieve audit log events for Portal retention details. With Telemetry Router, you can route your audit logs to external destinations.
- Complete history: The log records activities of both human users and automated system tasks for every service listed in Services with audit logs.
Benefits and use cases
Section titled “Benefits and use cases”Use the audit log to:
- Support governance and compliance: Meet regulatory requirements by keeping security-relevant audit trails that document your sequence of actions for auditors.
- Improve traceability: Trace changes to identify who performed an action and when. This provides transparency and accountability for your entire team.
- Resolve problems: Troubleshoot system issues by tracking the historical progression of events to find a root cause.
- Optimize performance: Use log insights to identify bottlenecks or inefficient manual processes that you could automate.
Service coverage
Section titled “Service coverage”To find out which services write audit log events and which service.name value identifies each of them, see Services with audit logs.
Audit event fields
Section titled “Audit event fields”Audit events share a common set of fields. The table lists each field’s presence, format, and meaning. Unless noted, values are strings. Required fields are present in every audit event. Optional fields can be absent. Conditional fields are present when the service has the corresponding value.
| Field | Presence | Values or format | Description |
|---|---|---|---|
body |
Required | Free text | Summary of the event |
client.address |
Optional | IP address | Network address of the client |
cloud.region |
Required | For example, global, eu01, or eu02 |
Region of the event |
http.request.method |
Optional | HTTP method | Method of the API request |
server.address |
Optional | API hostname | Host of the API request |
service.instance.id |
Required | ID or name | Affected instance |
service.name |
Required | Service identifier | Service that wrote the event |
severityText |
Required | TRACE, DEBUG, INFO, WARN, ERROR, or FATAL |
Severity of the event |
stackit.action |
Required | Action from the service event catalog, in the form product.target.verb, for example secrets-manager.instance.create |
Action that caused the event |
stackit.initiator |
Required | User or service account ID, or SYSTEM |
Actor that caused the event |
stackit.initiator.email |
Conditional | Email address | Email address of the initiator |
stackit.log.id |
Required | Unique event ID | Identifies the event |
stackit.log.type |
Required | AUDIT |
Type of the log entry |
stackit.request.body |
Required | Original request body, encoded as a string; can contain sanitized fields | Request that caused the event |
stackit.resource.id |
Required | ID of the project, folder, or organization | Resource containing the event |
stackit.resource.type |
Required | PROJECT, FOLDER, ORGANIZATION, SYSTEM, or another value |
Type of the containing resource, Telemetry Router cannot route events with another value to the owner |
stackit.response.body |
Optional | JSON encoded as a string, can be empty | Response to the request |
stackit.visibility |
Required | PUBLIC |
Visibility of the event |
timeUnixNano |
Required | Unsigned 64-bit integer, Unix time in nanoseconds, a decimal string in JSON | Time of the event |
url.path |
Optional | API path | Path of the API request |
user_agent.original |
Optional | Client user agent | Client software that made the request |
The stackit.request.body and stackit.response.body values are JSON strings, not nested JSON objects. For service-specific fields, see the relevant page in Services with audit logs. For the action values of Telemetry Router and Telemetry Link, see Audit events of Telemetry Router.
Telemetry Router delivers each audit event as an OpenTelemetry log record. body, severityText, and timeUnixNano are fields of the log record. All other fields in the table are attributes of the log record, and events can carry further attributes:
{ "timeUnixNano": "1775575194605756000", "severityText": "INFO", "body": { "stringValue": "API Key 'key-9982' was successfully deleted by user." }, "attributes": [ { "key": "stackit.action", "value": { "stringValue": "secrets-manager.apikey.delete" } }, { "key": "stackit.initiator", "value": { "stringValue": "1472b021-f261-4bac-86cb-931a6759b7a2" } } ]}