On Mar 12, 5:00 am, Jaume Sabater <[email protected]> wrote: > Hello everyone! > > I am setting up the Zabbix monitoring solution at work. Among others, > beanstalkd is something I want to monitor. By executing the following > command I get the attached stats, which I am caching to a file > (example taken from a test server): > > echo -e 'stats\r' | socat - tcp4-connect:localhost:11300 > > I know this is a partly objective, partly subjective question but I > was wondering what I would really be interested in monitoring. I have > created items for the 45 values and I am now deleting the ones I don't > think I need. I think that I should not go beyond knowing/getting: > > 1. It's alive and working fine. > 2. A few counters on "how busy it is at the moment" > 3. A few counters on max values reached. > > IMHO, things such as version, max job size or max bin size are not > worth it. All the total-* and current-* (or most of) look nice but, > what about the cmd-*? > > Any hints? Anyone has done this before, and for a while, and could > provide real life experience?
Have a look at Dustin's beanstalk tools at http://github.com/dustin/beanstalk-tools I use some of these scripts with Nagios and I'm sure they can be easily integrated with Zabbix. - Brandon -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
