A log stream defines how log data is collected and delivered to a configured destination.

Streams operate in near real time, gathering events from supported services and batching them for delivery to a destination. Once a stream is active, it automatically delivers logs for all eligible services in your account—you don't need to create separate streams per service.

Stream types

There is currently only one supported stream type: audit logs.

• Audit logs. An audit log stream captures information about control plane events for your Akamai Cloud services, including what happened, who initiated the action, and when. An audit log stream delivers login and configuration audit logs to your configured destination in structured JSON Lines (JSONL) format.

For more information about the logs delivered by this stream type, see Log formats and content.

Stream configuration settings

A stream includes the following configuration settings:

• Name. A unique name for the stream. Stream creation will fail if the name already exists.

• Type. The category of log data the stream collects.

• Destination. The destination that receives the batched logs collected by the stream. See Log destinations for more information.

Stream activation

Streams are active by default when they're created. You can Activate or Deactivate at any time from the a stream's options menu.

Streams have the following states:

• Provisioning: Backend resources are being set up. Log delivery begins once the stream becomes active.
• Active: The stream is enabled and collecting audit logs, which are being delivered to the configured destination.
• Inactive: The stream configuration exists but log delivery is paused.

📘

After a stream becomes active, it may take up to 45 minutes for logs to begin arriving at the destination.

Stream versions

Each time you create or update a stream, a new version is generated. For example, modifying a stream's settings or changing the destination creates a new version.

Versioning provides visibility and traceability for long-lived or frequently updated streams.

Versioning behaves as follows:

• Previous versions are retained.
• The version with the highest version number is the active version.

You can use the API to retrieve a stream's version history to review past configurations and understand how the stream has changed over time.