I originally wrote the klog tool as a way of examining dumps of Kafka log files to find hanging transactions (before KIP-664).
 

People from support (rhn-support-fvaleri, at least) occasionally use it useful when dealing with customer problems. It's useful because:

1. It's at least partially tested, so more reliably correct than trying to do some ad hoc scripting.
2. It also embeds knowledge of specific problems (handing transactions, but it needn't be limited to that).

Since I wrote it the dump format has changed, so it's now less useful than it was.

We should review the functionality it provides (in the light of KIP-664) and consider improving it where it still provides value.