Larger Scope Message Viewer Proposals

[jlrobins]

Proposal for discussion

1. Be able to save message viewer state to a new file format, first w/o the messages themselves, but later on also optionally with the messages (see next). Probably piggybacks on the serialization needed to restore view when tabbing back and forth. Motivation: to configure view state, then save to disk, say, for needing to reboot, or perhaps to then xfer to a debugging buddy. Upon loading, if cannot access the cluster / topic, then have a new complaint view, perhaps asking user to log in? When loaded back, perhaps will start out in 'paused' mode? File is ultimately something like gzipped json.

2. Extend the above format to also include either:
   a. all of the currently streamed messages
   b. the current filtered streamed messages
   so that the exact set of messages you're looking at can be preserved and restored quickly and offline. And / or be transferred to a debugging buddy in known fixed amount of time (the time to xfer the file).

3. Convert the 'view individual message' to custom document provider like was done for schemas, so that don't always have to be prompted to 'are you sure you want to close' ? Then implement the message diffing just like is done for schemas. Need to also then be able to explicitly save file if desired, though.

4. Have a row in middle of the page, before the message columns, representing each filter in play -- any time range filter, any plaintext search, partition, etc. User can then easily see that they have N filters in context right now, and can then hit an 'X' that shows up when hovering over an individual filter to then remove it.

5. Ability to enter some sort of either jq or jsonpath expression to then become a new filter -- in addition to existing sub-string filtering.

6. Ability to enter some sort of either jq or jsonpath expression to become new message table column, extracted out from the message value payload.