Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • HTTP::Webtest might be useful. It's actively developed and easy to use.

    You should be able to cron an almost-one-liner that greps webtest output and does something when it find failed tests.

    • That is beautiful. You have no idea how much goodwill this is going to earn me... can I buy you a beer or pizza or name my next child after you?

      Wow. Here I thought this whole blog thing was just going to be an excercise in talking to myself... in the first day, I've been handed a raise by a complete stranger. Pretty soon, I'm going to be running for Governor of California!

      • Also look at Test::* together with WWW::Mechanize. I've got a major client doing that, and I'll be doing some column articles on it as well.
        • Randal L. Schwartz
        • Stonehenge
        • I'll look forward to those articles...

          HTTP::WebTest looks quite capable, but I'm always looking for a better way to do things.

          On a totally separate topic, I wish I could have joined you for the Alaska Perl Mongers barbecue when you were up here at the end of the last Geek Cruise... I trust you enjoyed your trip?

  • I got some email on a new monitoring thing called Covalent Application Manager (CAM). It looks like a full-blown monitoring solution with lots of reporting. I'm trying to find time to evaluate it. I did sit in on one webinar and it looks promising.

    Covalent [] does apache stuff, so they should have a good step up on monitoring. Don't yet know how much $, but looks like it might be pricey.
    • Thanks! I'll take a closer look, but from what I can tell HTTP::WebTest will probably do it for us. I'll keep you posted. Stay tuned...