See Kafka topics, partition leaders and ISR at a glance
List Kafka topics and inspect every partition's leader, replica count and in-sync replicas. Supports SASL/PLAIN, TLS and SSH tunnels to private brokers.
Transport: kafka-go, with optional SASL/PLAIN and TLS (port 9092 by default)
What you can do today
- Topic discovery from cluster metadata
- Partition leaders, replica counts and in-sync replica counts per partition
- Metadata for one topic, or for all topics at once
- SASL/PLAIN authentication and TLS with certificate verification
- SSH tunnels, including connections to the brokers' advertised addresses
Not supported yet
- Reading or producing messages
- Consumer groups and lag
- SASL/SCRAM authentication
Answer “is this topic healthy?” quickly
When a consumer stalls or a producer times out, the first questions are about metadata: does the topic exist, how many partitions does it have, which broker leads each one, and are all replicas in sync? DevOpsPad answers those without a CLI, a JVM or a web console running inside the cluster.
The Explorer lists every topic from the cluster metadata. Open one, or type its name in the editor, and the result has one row per partition:
# Kafka editor: a topic name, or "topics" for all topics
order.created
topics| Column | Meaning |
|---|---|
topic |
Topic name |
partition |
Partition ID |
leader |
Broker ID currently leading the partition |
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. Filter and sort the grid to find them, or export the table to CSV for an incident note. Results stop at 500 rows.
Authentication and private brokers
The connector supports SASL/PLAIN with a username and password, and TLS with certificate verification. Credentials are stored in the macOS keychain.
Brokers inside a VPC can be reached through an SSH tunnel. Kafka clients connect again to the addresses each broker advertises, and DevOpsPad sends those connections through the tunnel too. That means the advertised listener addresses have to resolve and be reachable from the SSH server. If the first metadata call succeeds and later calls fail, check the SSH troubleshooting guide.
Read-only by design
The Kafka adapter exposes no mutations. You cannot create, delete or reconfigure topics from DevOpsPad, and there is no producer. That keeps it safe to point at a production cluster while you investigate. Messages, consumer groups and SCRAM authentication are not available yet.
For more engines see the connector list, or how Redis key browsing works.
Help articles
Inspect Kafka topics and partitions
Connect DevOpsPad to Kafka with optional SASL/PLAIN and TLS, list topics and see each partition's leader, replica count and in-sync replica count.
Connect through an SSH tunnel
Reach private MySQL, Redis, MongoDB, Kafka, ClickHouse and Kubernetes endpoints through a bastion with DevOpsPad's built-in single-hop SSH tunnel.
Troubleshoot SSH tunnel errors
Fix DevOpsPad SSH tunnel errors - unreachable bastions, failed authentication, forwarding, Kafka advertised listeners, TLS names and unsupported setups.
Use TLS with database connections
How the Use TLS with certificate verification option works for MySQL, ClickHouse, MongoDB, Redis and Kafka in DevOpsPad, and what TLS setups are not supported.
Frequently asked questions
Can DevOpsPad read messages from a Kafka topic?
Not yet. The Kafka connector reads cluster metadata only, which is topics, partitions, leaders and replicas. Message preview and consumer groups are on the roadmap.
How do I see partition leaders for a single topic?
Type the topic name in the editor and run it. Type topics instead to list partitions for every topic in the cluster.
Why does a Kafka connection through SSH fail after the first broker responds?
Kafka clients reconnect to the addresses each broker advertises. Through a tunnel those advertised addresses must be reachable from the SSH server, not from your laptop.