News for hackers. Stuff that matters.
Re:Show HN: Redis Dashboard by antirez on Sunday June 17, 2012 @04:48PM (#4123796)
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 by nkrode on Sunday June 17, 2012 @04:50PM (#4123802)
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 by nkrode on Sunday June 17, 2012 @04:54PM (#4123815)
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 by antirez on Sunday June 17, 2012 @05:02PM (#4123828)
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 :)
Re:Show HN: Redis Dashboard by nkrode on Monday June 18, 2012 @12:35AM (#4125004)
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.
Re:Show HN: Redis Dashboard by djtriptych on Sunday June 17, 2012 @05:38PM (#4123910)
Worth browsing the code just to see some very well organized source for a tornado+redis+backbone stack, which is pretty popular I think on the real-time web.
Re:Show HN: Redis Dashboard by nkrode on Monday June 18, 2012 @01:07AM (#4125077)
thanks, i think the javascripts can use some bundling love.
Re:Show HN: Redis Dashboard by ya3r on Sunday June 17, 2012 @06:11PM (#4123991)
When I see these things I always wonder, what is the best way to integrate these monitoring stuff into your existing stack.

So server restarts and failures are just okay.

Anyone used similar monitoring utilities in production?

Re:Show HN: Redis Dashboard by true_religion on Sunday June 17, 2012 @05:54PM (#4123950)
This is the first one I've seen that uses Python as a backend.

Since Python is all I use in my shop, you've earned yourself my dearest thanks and a new follower.

Re:Show HN: Redis Dashboard by drewolson on Monday June 18, 2012 @10:05AM (#4126450)
I noticed you're using tornado but appear to be using the standard (non-evented?) python redis library. Does using this library block tornado's event loop? Did you look at other tools like brukva[1]?

[1] https://github.com/evilkost/brukva

Re:Show HN: Redis Dashboard by nkrode on Friday June 22, 2012 @01:44AM (#4145583)
brukva looks interesting, i'll check it out. thnx.
Re:Show HN: Redis Dashboard by billrobertson42 on Sunday June 17, 2012 @08:02PM (#4124249)
The text for the upper boxes is easy to read on the full sized png, but difficult when scaled when showing in the github page. If the smaller size is the default it could be an issue.

I also think you should make scales for "Used Memory" and "Memory Consumption" the same.

Looks good though.

Re:Show HN: Redis Dashboard by nkrode on Monday June 18, 2012 @01:12AM (#4125087)
the screenshot has been resized, the text is much larger otherwise.

agreed on the scales.

Re:Show HN: Redis Dashboard by steelthread666 on Monday June 18, 2012 @06:25PM (#4128920)
Looks somewhat similar to something a wrote a few months back. http://steelthread.github.com/redmon/. Your solution looks good, well done.
Re:Show HN: Redis Dashboard by nkrode on Friday June 22, 2012 @01:41AM (#4145578)
cool, i like the CLI interface - i was thinking of doing a similar widget too. are you still actively working on that project?
Re:Show HN: Redis Dashboard by JOnAgain on Sunday June 17, 2012 @04:18PM (#4123703)
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 by nkrode on Sunday June 17, 2012 @04:48PM (#4123797)
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 by grungleshnorts on Sunday June 17, 2012 @04:37PM (#4123761)
Re:Show HN: Redis Dashboard by daa on Sunday June 17, 2012 @04:11PM (#4123686)
Nice! I've been looking for something to give me a better feel for what's going on.
Re:Show HN: Redis Dashboard by vailripper on Monday June 18, 2012 @12:51AM (#4125051)
This looks awesome. Anyone know of a similar project for MongoDB?
Re:Show HN: Redis Dashboard by nkrode on Monday June 18, 2012 @01:08AM (#4125080)
we can easily extend this for MongoDB, if you are interested lets connect.
Re:Show HN: Redis Dashboard by vailripper on Thursday June 21, 2012 @05:51PM (#4144378)
Unfortunately my free time is a bit swamped with some side projects right now - will definitely get in touch when things die down.
Re:Show HN: Redis Dashboard by bsg75 on Monday June 18, 2012 @03:53PM (#4128162)
Mongolive, a Chrome plugin, may be similar.
Re:Show HN: Redis Dashboard by vailripper on Thursday June 21, 2012 @05:57PM (#4144396)
Interesting, i'll take a look.