Kafka Plugin

The Kafka plugin registers an Apache Kafka cluster as one Konduo resource and exposes broker, controller, topic, partition, and consumer group state as operational evidence.

Highlights

• Uses bootstrap servers as seeds and validates broker listeners and cluster id from Kafka metadata.
• Exposes KRaft/controller roles, broker inventory, topic/partition state, consumer group lag, and offset evidence.
• Connects JMX/exporter-style metrics through a Prometheus mapping pack.
• In mixed collection mode, broker metrics stay external while Konduo collects consumer group lag through the Kafka Admin API.

Before Registration

• Prepare bootstrap servers, security protocol, SASL, TLS, and timeout settings.
• Confirm that advertised broker listeners are reachable from the Konduo backend.
• For managed consumer group lag collection, prepare Admin API access and a remote-write target.

Operations Tips

• A down bootstrap broker does not always mean the whole cluster is unavailable if discovered broker endpoints still work.
• Read consumer lag with total lag, max lag, member state, and offset movement together.
• Topic partition changes, reassignment, throttles, ACLs, and quotas run behind permission and confirmation boundaries.

---

Kafka Enterprise Overlay

The Kafka Enterprise overlay adds MCP descriptors and anomaly rule metadata on top of the Community Kafka plugin.

Highlights

• Exposes monitoring overview, diagnostics, consumer groups, security operations, metrics mapping, and anomaly rules through the MCP catalog.
• Evaluates anomaly rules in declarative_metric mode by resolving Kafka logical metrics through metric-source mappings.
• Mutating workflows such as reassignment, broker drain, replica changes, topic changes, and message actions keep the existing Konduo API, RBAC, and audit boundaries.
• Treats bootstrap addresses as seeds and interprets broker inventory with advertised listener evidence.

Common Uses

1. Inspect Kafka operational state through MCP resources and tools
2. Explore broker, partition, and consumer group state in read-oriented workflows
3. Review the Enterprise anomaly rule catalog
4. Connect dashboards and diagnostics to agent workflows

Before Registration

• Kafka connectivity and permissions follow the Community Kafka plugin settings.
• The MCP gateway and related authorization profile must be enabled before MCP descriptors are usable.
• Anomaly rules operate in environments where the Enterprise analysis engine is enabled.

Operations Tips

• Use MCP tools for operational lookup and analysis assistance; configuration changes should still follow Konduo UI and approved procedures.
• Anomaly rules do not replace alert rules; treat them as supporting signals for correlation and incident analysis.
• For consumer lag analysis, review total lag, max lag, member state, offset movement, and controller state together.