I must say its been an enlightening experience, this thread.

I may be treading off topic here, but your advice was really worthwhile and I would like to share what I'm looking to accomplish at the moment.

We have OpenView Operations (OVOW) as our systems maangement tool, and I've worked previously with Network Node Manager, however it doesn't seem our comapny's too keen to go that direction just yet.

All the services we provide are web-based applications hosted on multiple portals, so what we need here is basically an internet services monitoring and reporting application. This script is a first step in that direction and will be run as a scheduled task from OVOW and send integrated events on failure.

Once I have this in place I'll continue searching for ways in which we can enahnce the website monitoring and reporting.

by the way, in your opinion is this script robust enough to be used for this kind of monitoring. Is it possible to run the get command multiple times in the same script and having a correlation of three consecutive not 200 OK results to be reported as a single failure

Looking forward to continue my learning


In reply to Re^4: LWP for URL monitoring - 500 connect timeout errors by Anonymous Monk
in thread LWP for URL monitoring - 500 connect timeout errors by oalvi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.