Skip to content

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)

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.

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.

To find out which services write audit log events and which service.name value identifies each of them, see Services with audit logs.

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.

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" }
}
]
}