DevOpsPadDownload

Inspect Kafka topics and partitions

DevOpsPad shows Kafka cluster metadata: the list of topics and, for each partition, the leader broker ID, the number of replicas and the number of in-sync replicas. Type a topic name in the editor and run it to see that topic’s partitions, or type topics to see every partition of every topic.

It does not read or produce messages. The Kafka adapter exposes no mutations, so it is safe to point at production brokers.

Connect

  1. Click New connection and choose Kafka. The port starts at 9092.
  2. Enter a broker Host and Port. This is the bootstrap broker DevOpsPad asks for metadata.
  3. For SASL/PLAIN, enter Username and Password. Leave both empty for brokers without authentication.
  4. Turn on Use TLS with certificate verification if the listener uses TLS.
  5. Click Test connection. DevOpsPad sends a metadata request. Then click Save connection.

Kafka connections have no Database field.

Read topic and partition metadata

Select the connection. The Explorer lists topics by name, including internal topics such as __consumer_offsets. Click a topic to open a tab with its name, then run it:

order.created

Or list every partition in the cluster:

topics
Column Meaning
topic Topic name
partition Partition ID
leader Broker ID of the current partition leader
replicas Number of assigned replicas
in_sync_replicas Number of replicas in the ISR

A partition where in_sync_replicas is lower than replicas is under-replicated: at least one follower has fallen behind or its broker is down. A topic name that does not exist returns the broker’s error instead of an empty table.

TLS and SASL

With TLS on, DevOpsPad requires TLS 1.2 or later and verifies each broker’s certificate against its own advertised host name, not only the bootstrap host. SASL/PLAIN sends the password inside the TLS session; do not use SASL/PLAIN without TLS outside a trusted network.

Brokers behind SSH

Kafka clients connect to the addresses brokers advertise, not just the bootstrap address. With Connect through SSH tunnel, those advertised connections also go through the tunnel, so every advertised address must be reachable and resolvable from the SSH server. If metadata loads through the bootstrap broker but other requests fail, check the brokers’ advertised.listeners. See SSH troubleshooting.

Limits

  • Messages, consumer groups, offsets and lag are not available.
  • SCRAM authentication is not supported; SASL/PLAIN only.
  • Results stop at 500 partitions per query. See result limits.
  • Custom CA certificates are not configurable yet.

Frequently asked questions

Can DevOpsPad read Kafka messages or consumer group lag?

Not yet. This version reads cluster metadata only, topics, partitions, leaders and replica counts. Message browsing, consumer groups and SCRAM authentication are not available.

Which SASL mechanism does DevOpsPad use for Kafka?

SASL/PLAIN. When you enter a username, DevOpsPad authenticates with SASL/PLAIN. SCRAM-SHA-256 and SCRAM-SHA-512 are not supported yet.