For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/data_streams/kafka/setup.md. A documentation index is available at /llms.txt.

Kafka Console Setup

This product is not supported for your selected Datadog site. ().

This page covers the prerequisites and setup steps for Kafka Console.

Prerequisites

Datadog Agent version

Datadog Agent version 7.78 or later is required.

ACL permissions

If your Kafka cluster uses ACLs, the Datadog Agent user requires the following minimum permissions:

Resource NameResource TypeOperation
kafka-clusterCLUSTERDescribe
kafka-clusterCLUSTERDescribeConfigs
*TOPICDescribe
*TOPICDescribeConfigs
*GROUPDescribe

Setup

Enable Kafka Console by setting enable_cluster_monitoring: true in the Kafka Consumer integration.

For additional environment-specific guidance on configuring the integration, go to the Kafka Console setup page and click Get Started. Then choose your environment and follow the instructions.

The Kafka Console setup dialog showing environment selection, security protocol, schema registry options, and Kubernetes configuration instructions

You can copy the setup instructions directly to an AI agent with Copy for AI.

Enable Kafka actions

Kafka actions let you read messages, create topics, and delete topics from Kafka Console. This section applies only if you want to use these actions. Skip it if you only need monitoring.

Remote configuration

Remote configuration must be enabled at three levels:

  1. At the organization level.
  2. At the Agent level.
  3. At the API key level.

Additional ACL permissions

The Datadog Agent runs each action on your Kafka cluster. In addition to the ACL permissions listed in Prerequisites, grant the Agent user the ACLs for each action you plan to use:

ActionResource NameResource TypeOperation
Read messages*TOPICRead
Create a topic*TOPICCreate
Delete a topic*TOPICDelete

The * resource name applies the operation to all topics. To restrict an action to specific topics, replace * with those topic names.

User permissions

Each action requires a user permission:

ActionPermission
Read messagesData Streams Monitoring Capture Messages
Create a topicData Streams Monitoring Kafka Create Topic
Delete a topicData Streams Monitoring Kafka Delete Topic

Datadog records each Kafka action in Audit Trail under the Data Streams Monitoring category. Each entry includes the user, topic, and cluster.

Deleting a topic permanently removes the topic and all of its messages. Grant the Data Streams Monitoring Kafka Delete Topic permission only to users who manage your Kafka topics.

You can verify your current permissions on your Profile page. To enable permissions, edit an existing role or create a role on the Roles page. If you do not have permission to modify roles, contact your organization’s administrator.

1. Create a role

  1. Navigate to the Roles page in Datadog.
  2. Click + New Role in the top-right corner.
    If you see "Read Only" instead of the "+ New Role button", you don't have permission to create roles. Contact your Datadog administrator for assistance.
  3. Enter a descriptive name for your role (for example, “Kafka Actions Access”).
  4. In the Search Permissions field, enter the name of a permission from the User permissions table (for example, Data Streams Monitoring Capture Messages).
  5. Select the permission from the search results to enable it for this role. Repeat for each permission you want to grant the role.
  6. Click Save.
  7. Confirm your role was created successfully by searching for it in the roles list.

2. Assign the role to users

  1. Go to the Users page in Datadog.
  2. Find and click on the user you want to assign the role to.
  3. In the user details panel, click Edit next to their name.
    If you don't see an Edit button, you need administrator privileges to modify user roles. Contact your Datadog administrator.
  4. In the modal that opens, locate the Roles section.
  5. Add your newly created role to the user.
  6. Click Save.
  7. Look for a User updated confirmation message to verify the change was successful.

Further reading