feat: Add OTel Kafka Docs pages #22575
Draft
+7,292
−1,080
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add OpenTelemetry Kafka Monitoring Documentation
📋 Overview
This PR adds comprehensive documentation for monitoring Apache Kafka using OpenTelemetry. The documentation covers self-hosted and Kubernetes (Strimzi) deployments with detailed configuration examples, metrics reference, and best practices.
🎯 What's Changed
New Documentation Pages
Created 4 new documentation pages under
/docs/opentelemetry/integrations/kafka/:Documentation Structure
/docs/opentelemetry/integrations/kafka/
├── overview.mdx # Overview and architecture
├── self-hosted.mdx # Self-hosted deployment
├── kubernetes-strimzi.mdx # Kubernetes/Strimzi deployment
└── metrics-reference.mdx # Complete metrics reference
🔑 Key Features
Metrics Collection
Kafka Metrics Receiver: Cluster-level metrics (13 metrics)
JMX Receiver (Default): Broker and cluster metrics (21 metrics)
JMX Receiver (Custom): Extended metrics (17 metrics)
Client Metrics: Application-level observability (200+ metrics)
Deployment Options
✅ Self-hosted: Linux systemd service with dual-pipeline architecture
✅ Kubernetes: Strimzi integration with receiver_creator for dynamic broker discovery
✅ Client instrumentation: Zero-code Java Agent instrumentation for producers/consumers
Advanced Configuration
broker.idattribute📁 Files Changed
Added
/docs/opentelemetry/integrations/kafka/overview.mdx(new)/docs/opentelemetry/integrations/kafka/self-hosted.mdx(new)/docs/opentelemetry/integrations/kafka/kubernetes-strimzi.mdx(new)/docs/opentelemetry/integrations/kafka/metrics-reference.mdx(new)/static/images/Modified
/docs/infrastructure/host-integrations/host-integrations-list/kafka/index.mdx/src/nav/infrastructure.yml/src/nav/opentelemetry.yml/src/nav/message-queues-streaming.yml🗺️ Navigation Updates
Updated navigation across three files for better discoverability:
infrastructure.yml - Under "On-host integrations"
opentelemetry.yml - Under "Integrations"
message-queues-streaming.yml - Under "Install integrations"
📸 Screenshots Added
infrastructure_screenshot-crop_otel-kafka-dashboard-clusters-view.webpinfrastructure_screenshot-crop_otel-kafka-entity-explorer.webpinfrastructure_screenshot-crop_otel-kafka-Q&S-summary.webpinfrastructure_screenshot-crop_otel-kafka-third-party-integrations.webpinfrastructure_screenshot-crop_otel-kafka-dashboard-brokers-view.webp🎨 Kafka Index Page Improvements
Updated
/docs/infrastructure/host-integrations/host-integrations-list/kafka/index.mdx:🔧 Technical Details
Dual-Pipeline Architecture
Broker Pipeline (includes
broker.id):Cluster Pipeline (removes
broker.id):Client Telemetry Flow
Metrics Coverage Matrix
📚 Example Configurations
Self-hosted: Dual-Pipeline Setup
Kubernetes: Dynamic Broker Discovery
Metrics Reference
✅ Testing Checklist
🚫 Breaking Changes
None. This is purely additive documentation.
🔍 SEO & Discoverability
Multiple navigation references improve discoverability without creating duplicate content:
📖 Related Documentation
👥 Review Focus Areas
📝 Notes for Reviewers
/docs/opentelemetry/integrations/kafka/locationDeployment: Self-hosted Linux and Kubernetes (Strimzi)
Monitoring Scope: Broker, cluster, topic, partition, consumer group, and application metrics
Integration Method: OpenTelemetry Collector + optional Java Agent instrumentation