Audit Logs
This page describes how to setup WarpStream Audit Logs.
Introduction
WarpStream Audit Logs provide a way to capture, protect, and preserve Kafka authentication actions, authorization actions, and organization operations into a Kafka topic for Pro and Enterprise clusters. Audit logs also track account-level operations such as creating, deleting, and modifying WarpStream resources such as API keys, Kafka clusters, user accounts, etc.
WarpStream Audit Logs are produced into a fully-managed WarpStream cluster deployed on WarpStream's cloud infrastructure. Audit Logs can either be accessed through the WarpStream Console, or consumed using the Kafka protocol and exported anywhere. Audit Logs are retained for 90 days.
Getting Started
Pre-requisites: you need to use the agent version v736 or above.
In order to enable Audit Logs, navigate to the "Audit" section from the Console left panel.
Once enabled Audit Logs will start flowing:
Cluster audit logs: all Pro and Enterprise clusters will emit audit logs (following the convention described here)
Platform audit logs: all requests to the WarpStream console except GET requests will emit an audit log
Audit Logs are visible under the "Events" tab.
To consume Audit Logs using a Kafka client, follow the instructions for connecting to the cluster in the Audit section.
Audit Logs structure
WarpStream audit logs follow the CloudEvents spec and conform to the schema described here.
Here are a few examples:
A Kafka failure
A Kafka success:
A platform success:
Consume Audit Logs
Under the "Credentials" tab of the audit page, users can create SASL credentials that can then be used to consume from the Audit Logs topic. The "Connect" tab contains everything you need to know to start consuming with code samples.
Last updated
Was this helpful?