A changelog restore records its progress only in a local checkpoint file

The missing term is what makes restore progress uncomputable from outside. A read-only observer can read how far each changelog topic reaches ^[12]. The instance's own position in that changelog is in the local checkpoint file, so records remaining is a subtraction with one term unpublished ^[17]. Meanwhile input keeps arriving, and group lag climbs for a reason the cluster has no way to report ^[5]. Alginte's example of the case is a stream replaying 7.5 million changelog records after its state directory was wiped, beside a cluster view of a stable group ^[11].

The state relabelling is the piece I would copy into anything that reads a Streams client. Both cases the console rewrites are ones where the client enum is accurate about the client and wrong about whether records are moving: REBALANCING with every thread dead, and RUNNING with assigned tasks served by nobody ^[8]. The per-partition figure works the same way. One column per store partition, interpreted by role, showing records left to replay during a restore, distance behind the active for a standby, and plain changelog lag at steady state ^[9].

Threads, rebalance counts with their durations and an event timeline sit on the same tab, and the restore banner appears only while a store is actually replaying ^[7]. Next to all of it the console puts the cluster's own facts about the same stream, group state, committed offsets and changelog topics, so the two accounts can be checked against each other ^[10].

None of that depth comes from a smarter query. It exists because the console runs the stream, holds the Kafka Streams client and reads it in process, with no agent, no scraping and nothing written to the cluster ^[6]. Alginte calls the cluster-only view "the depth the cluster allows" and says it is "where the idea points next" ^[16]. The post does not state pricing or licence terms ^[18].

One display rule is worth holding other monitors to: every figure the observer cannot see is a dash, never a zero ^[13]. The post gives its reason for refusing to display a lifecycle it cannot verify, which is that "a group reads stable while threads die and we would rather show absence than invent one" ^[14].

The design-time half of the product is a separate argument. The modeler draws the topology node by node. Each operator carries the expression it applies, the editor shows a record that is really in the source topic beside what the expression makes of it, and the derived shape at each node is marked inferred ^[15].

All of the above is Alginte describing its own console, and the run-time behaviour is single-sourced.