Scout monitoring Redis

15 views
Skip to first unread message

Matt Todd

unread,
Dec 1, 2009, 3:18:39 PM12/1/09
to Redis DB
Hey, here's a quick snapshot of Scout monitoring Redis:

http://skitch.com/mtodd/njabd/scout-master

Just thought someone would find this interesting. I just whipped up the plugin really quickly:

Interesting to note that my memory profile stays pretty consistent whereas there are obviously many changes going on. Just part of how this particular application works: I expire as much data as comes in.

Matt



--
Matt Todd
Highgroove Studios
www.highgroove.com
cell: 404-314-2612
blog: maraby.org

Scout - Web Monitoring and Reporting Software
www.scoutapp.com

Salvatore Sanfilippo

unread,
Dec 1, 2009, 5:37:56 PM12/1/09
to redi...@googlegroups.com
On Tue, Dec 1, 2009 at 9:18 PM, Matt Todd <mt...@highgroove.com> wrote:
> Hey, here's a quick snapshot of Scout monitoring Redis:
> http://skitch.com/mtodd/njabd/scout-master
> Just thought someone would find this interesting. I just whipped up the
> plugin really quickly:
> http://github.com/mtodd/redis-info/raw/master/redis.rb

Thanks for sharing!

> Interesting to note that my memory profile stays pretty consistent whereas
> there are obviously many changes going on. Just part of how this particular
> application works: I expire as much data as comes in.

Yes indeed, I wonder if you are using or not 'maxmemory' (I guess no).

Cheers,
Salvatore

--
Salvatore 'antirez' Sanfilippo
http://invece.org

"Once you have something that grows faster than education grows,
you’re always going to get a pop culture.", Alan Kay

Matt Todd

unread,
Dec 1, 2009, 5:49:43 PM12/1/09
to redi...@googlegroups.com
I'm using the used_memory information from the INFO command. I'm actually slightly transforming this output (adding a space after the :) so that I can parse as YAML and then just reporting on these numbers.

If you're asking if I'm even close to maxing out my memory, I have plenty of headroom. The design of the application actually only needs this data in Redis for an hour at a time and after that it can remove the data (I simply expire it an hour later, just in case I need to debug something in the process). The intent is to watch carefully how big this gets as we add more load to the stack.

Here's the output from `redis-cli info` if you're curious:

redis_version:1.02
uptime_in_seconds:746002
uptime_in_days:8
connected_clients:2
connected_slaves:0
used_memory:227886921
changes_since_last_save:11357
bgsave_in_progress:1
last_save_time:1259707186
total_connections_received:7999
total_commands_processed:17110246
role:master
db0: keys=1379,expires=1020

Matt




--

You received this message because you are subscribed to the Google Groups "Redis DB" group.
To post to this group, send email to redi...@googlegroups.com.
To unsubscribe from this group, send email to redis-db+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/redis-db?hl=en.


Reply all
Reply to author
Forward
0 new messages