|
| 1 | +# Kafka Actions |
| 2 | + |
| 3 | +<div class="alert alert-danger"> |
| 4 | +This integration is in Preview. To access and use this feature, reach out to the Data Streams Monitoring team at Datadog. |
| 5 | +</div> |
| 6 | + |
| 7 | +## Overview |
| 8 | + |
| 9 | +The Kafka Actions integration enables one-time administrative and operational actions on Kafka clusters through the Datadog Agent. |
| 10 | + |
| 11 | +<div class="alert alert-warning"> |
| 12 | +This integration is exclusively triggered through [Remote Configuration][4] and should never be scheduled manually in your Agent configuration. It is not meant to run continuously like traditional checks. |
| 13 | +</div> |
| 14 | + |
| 15 | +### Supported Actions |
| 16 | + |
| 17 | +| Action | Description | |
| 18 | +|--------|-------------| |
| 19 | +| `read_messages` | Read and filter messages with jq-style expressions, supporting JSON, string, BSON, Avro, and Protobuf formats | |
| 20 | +| `produce_message` | Produce messages to topics with base64-encoded payloads and headers | |
| 21 | +| `create_topic` | Create topics with custom partitions, replication factor, and configurations | |
| 22 | +| `update_topic_config` | Update topic configurations and partition counts | |
| 23 | +| `delete_topic` | Delete topics | |
| 24 | +| `delete_consumer_group` | Delete consumer groups | |
| 25 | +| `update_consumer_group_offsets` | Reset consumer group offsets to specific positions | |
| 26 | + |
| 27 | +## Setup |
| 28 | + |
| 29 | +### Installation |
| 30 | + |
| 31 | +The Kafka Actions integration is included in the [Datadog Agent][1] package (version 7.0+). |
| 32 | + |
| 33 | +### Configuration |
| 34 | + |
| 35 | +<div class="alert alert-warning"> |
| 36 | +<strong>Do not configure this check manually</strong>. This integration is triggered exclusively through [Remote Configuration][4] from the Datadog UI. |
| 37 | +</div> |
| 38 | + |
| 39 | +Actions are configured and triggered from the Datadog platform, with results visible in the [Events Explorer][3]. |
| 40 | +Each instance should configure only **one** action. Multiple actions in the same instance are not supported. |
| 41 | + |
| 42 | +## Data Collected |
| 43 | + |
| 44 | +### Events |
| 45 | + |
| 46 | +- **Action Events** (`kafka_action_success` / `kafka_action_error`): Emitted when an action completes |
| 47 | +- **Message Events** (`kafka_message`): Emitted for each message retrieved by `read_messages` |
| 48 | + |
| 49 | +### Metrics |
| 50 | + |
| 51 | +This integration does not collect metrics. |
| 52 | + |
| 53 | +### Service Checks |
| 54 | + |
| 55 | +This integration does not include service checks. |
| 56 | + |
| 57 | +## Troubleshooting |
| 58 | + |
| 59 | +### Actions not executing |
| 60 | +1. Confirm the Agent version meets minimum requirements |
| 61 | +2. Verify [Remote Configuration][4] is enabled on your Agent. |
| 62 | +3. Check Agent logs for errors. |
| 63 | + |
| 64 | +### Message deserialization failures |
| 65 | +Ensure the correct format is specified (`json`, `string`, `bson`, `avro`, `protobuf`) and provide schemas for Avro/Protobuf. |
| 66 | + |
| 67 | +Need help? Contact [Datadog support][2] or reach out to the **Data Streams Monitoring team** at Datadog for questions about this integration. |
| 68 | + |
| 69 | +[1]: https://app.datadoghq.com/account/settings/agent/latest |
| 70 | +[2]: https://docs.datadoghq.com/help/ |
| 71 | +[3]: https://app.datadoghq.com/event/explorer |
| 72 | +[4]: https://docs.datadoghq.com/remote_configuration/ |
0 commit comments