I wonder what benefit distributed monitors are providing, over, say, running a single monitor and accumulating subsequent errors until a certain threshold is reached, before firing up an email to alert whoever's watching.

Let's say, there's a network glitch happening between Monitor1 and the target, but not between Monitor2 and the target. It's more than likely that the problem also occurs on the network between Monitor1 and the watcher. So while Monitor2 reports the error, Monitor1 can't get through to the watcher. What to do in this case? How can you decide if it's the monitor's fault, or the network's, or the target's?

In reply to Re: Distributed URL monitor by saintmike
in thread Distributed URL monitor by saetaes

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.