Skip to main content

​
Brokers

The Brokers page shows the cluster at a glance: a state card (controller id, node count, protocol version) and a table of every broker — controller flag, host, port, rack — each linking to its detail page. There is no create action here by design: brokers are cluster-managed. A broker’s detail page has three tabs:
  • Info — the broker’s identity and role.
  • Config — the broker’s effective configuration, searchable.
  • Topics/Partitions — which partitions this broker hosts, and its role for each (leader or replica) — the view you want when asking “what lives on this node?“.

​
ksqlDB

The ksqlDB entry appears in the sidebar when a ksqlDB server is configured (alginte.ksqldb.url — see Configuration). Three tabs:
  • Editor — a SQL editor with an execute button and a result panel. A mode switch distinguishes the two kinds of requests:
    • Statement — DDL/DML: CREATE STREAM …, INSERT INTO …, SHOW STREAMS;
    • Query — pull queries that return rows: SELECT … WHERE …;, with LIMIT for ranges.
  • Streams — the server’s streams (name, type, backing topic, key/value formats), refreshed automatically each time you return to the tab.
  • Tables — the same view for tables.
A minimal end-to-end session — create the riders topic first (Topics guide), then in Statement mode:
Then switch to Query mode for a point lookup:
The editor executes pull queries and statements. Continuous push queries (EMIT CHANGES) hold a connection open indefinitely and are rejected with a clear message — use a dedicated consumer (or the topic’s Live messages view) to follow a stream continuously.