Thanks antirez! yes i've been tracking the changes coming to MONITOR command with 2.6 and i'll probably update it once 2.6 releases.
Can you connect with me on twitter @nkrode
agreed on MONITOR command, i rather just use INFO however on our deployment, top keys and commands are usually the most important information i'm looking for and with 2.4 there is currently no way.
When full monitoring is needed (like for the top keys) but still the analysis must be run continuously on a production instance, maybe in the next version of MONITOR (already planned) we could say to it "give me N items and return back in normal mode", or a similar thing but with time (for instance 1 millisecond), so that it is possible to perform some kind of polling that has no serious impacts on the server. Well I'll think about this when I'll reimplement monitoring :)
In redislive, the monitoring duration is configurable via command line argument, the idea is to schedule it as a cron job and monitor every 6 hrs for 1-2 minutes, that's enough to build the trend for analytics.
About top-keys, no way to show this without MONITOR, but it's not the most important bit of the visualization IMHO.
So very cool but a tool like this should not try to capture the stream of the commands executed by instead rely on what the system can provide as already aggregated stats.