Set up Confluent Kafka instrumentation
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. The Elastic APM .NET agent enables you to trace the execution of operations in your .NET applications, sending performance metrics and errors to the Elastic APM server. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless Observability
Generally available
Stack
Generally available
APM Agent .NET
Generally available
| Package | Supported versions |
|---|---|
Confluent.Kafka |
≥1.4.0 <3.0.0 |
For the full compatibility matrix including supported installation methods, refer to Messaging systems.
This page assumes the core agent is already set up. If not, see Set up the APM .NET Agent first.
Confluent.Kafka does not natively emit OpenTelemetry activities. To enable tracing without the profiler, add Confluent.Kafka.Extensions.Diagnostics (a third-party package) to your project. This package wraps producers and consumers to emit OpenTelemetry activities, which the agent's built-in OpenTelemetry Bridge captures automatically.
Follow the setup instructions in the Confluent.Kafka.Extensions.Diagnostics package, in particular the producer configuration which requires explicit wrapping.
If you are using the Elastic APM Profiler, Kafka is instrumented automatically via IL rewriting for Confluent.Kafka ≥1.4.0 <3.0.0 with no code changes required. The Confluent.Kafka.Extensions.Diagnostics package is not needed in that case.