Live data from Hacker News

Show HN: Redis Dashboard

github.com

1–10 of 25 posts

Re: Show HN: Redis Dashboard

#3
sorry for not just digging through the source, but what are you using for the charts?

Are you storing metric data? or is it all in the browser? (e.g. do you get the full screen you just showed when you first open it up, or is it like a process mon where it's all 0 until you look at it)?

Re: Show HN: Redis Dashboard

#4
post #3

sorry for not just digging through the source, but what are you using for the charts? Are you storing metric data? or is it all in the browser? (e.g. do you get the full screen you just showed when you first open it up, or is it like a process mon where it's all 0 until you look at it)?

Looks like google charts/visualization.

https://github.com/kumarnitin/RedisLive/blob/master/src/www/...

Re: Show HN: Redis Dashboard

#5
Great output, but IMHO the data source should change to be just INFO and not MONITOR: with Redis 2.4 you can't show top-commands. With 2.6 INFO has enough data about this (see INFO commandstats).

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.

Re: Show HN: Redis Dashboard

#6
post #3

sorry for not just digging through the source, but what are you using for the charts? Are you storing metric data? or is it all in the browser? (e.g. do you get the full screen you just showed when you first open it up, or is it like a process mon where it's all 0 until you look at it)?

Using Google Charts.

For storing the data i have a sqlite implementation and a redis implementation. sqlite works out of the box by default, but i prefer the redis implementation, much faster. https://github.com/kumarnitin/RedisLive/blob/master/src/data...

Re: Show HN: Redis Dashboard

#7
post #5

Great output, but IMHO the data source should change to be just INFO and not MONITOR: with Redis 2.4 you can't show top-commands. With 2.6 INFO has enough data about this (see INFO commandstats). 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 r…

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

Re: Show HN: Redis Dashboard

#8
post #5

Great output, but IMHO the data source should change to be just INFO and not MONITOR: with Redis 2.4 you can't show top-commands. With 2.6 INFO has enough data about this (see INFO commandstats). 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 r…

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.

Re: Show HN: Redis Dashboard

#9
post #8
post #5

Great output, but IMHO the data source should change to be just INFO and not MONITOR: with Redis 2.4 you can't show top-commands. With 2.6 INFO has enough data about this (see INFO commandstats). 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 r…

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 :)
Post reply on HN