Data Streams Monitoring for Kafka

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Prerequisites

LanguageLibraryMinimal tracer versionRecommended tracer version
Javakafka-clients (Lag generation is not supported for v3.7)1.9.01.43.0 or later
Goconfluent-kafka-go1.56.11.66.0 or later
Sarama1.56.11.66.0 or later
Node.jskafkajs2.39.0 or 3.26.0 or 4.5.05.25.0 or later
confluent-kafka-javascript5.52.05.52.0 or later
Pythonconfluent-kafka1.16.02.11.0 or later
.NETConfluent.Kafka2.28.02.41.0 or later
Kafka Streams is partially supported for Java, and can lead to latency measurements being missed.

Supported Kafka deployments

Instrumenting your consumers and producers with Data Streams Monitoring allows you to view your topology and track your pipelines with ready-to-go metrics independently of how Kafka is deployed. Additionally, the following Kafka deployments have further integration support, providing more insights into the health of your Kafka cluster:

ModelIntegration
Self HostedKafka Broker & Kafka Consumer
Confluent PlatformConfluent Platform
Confluent CloudConfluent Cloud
Amazon MSKAmazon MSK or Amazon MSK (Agent)
Red PandaNot yet integrated

Setting up Data Streams Monitoring

See setup instructions for Java, Go, Node.js, Python, or .NET.

Monitoring Kafka Pipelines

Data Streams Monitoring uses message headers to propagate context through Kafka streams. If log.message.format.version is set in the Kafka broker configuration, it must be set to 0.11.0.0 or higher. Data Streams Monitoring is not supported for versions lower than this.