Hey, I never claimed it was particularly pretty or good code, but it works, and I couldn't find anything else like it, so I put it out there to help anyone else who was just looking for something quick and dirty to use. It has come in handy here over the past few days. I look forward to seeing your tool once it's released - there are a lot of things lacking from it that I didn't have the time or inclination to add, so it'll be good to have something a little more real to play with.
Thanks, Nicholas On Apr 22, 4:00 pm, gf <[email protected]> wrote: > Hi. It's really good idea, but your code is not good, IMHO. > I've started the same project now.. > It will be released soon. > > On 22 апр, 23:34, ntang <[email protected]> wrote: > > > Hey all. First post... > > > We've been using memcached for a while, but we've never really done > > much to monitor it past making sure the servers were up and running. > > Anyways, we recently had some issues that looked like they might have > > been related to memcached performance/ usage, and I figured it was > > about time that we started taking a look at it. We've added graphs > > for various stats so we can track them over time, and added nagios > > checks for the stats as well, but I also wanted a quick way to see the > > immediate state of the cluster. > > > So I wrote a little tool. Hopefully people will find it useful. It's > > mostly configured by editing a config block up top, sue me. It's > > cheesy but works. The first time you run it, you'll need (at a > > minimum) to populate @servers. > > > It's here:http://code.google.com/p/memcache-top/ > > > (In retrospect I should've named it memcached-top, but such is life. > > I think people will be able to figure it out, and maybe if I put out > > another 'release' (*cough*) I'll rename it. ;) ) > > > Thanks, > > Nicholas
