There are many systems for monitoring, alerting and event analysis and consolidation: both commercial packages and free software. For a large scale distributed system, I would use such a package rather than writing my own.
You need to consider how to send a reasonable number of alerts that come as close to identifying the root cause of the fault as practical. For example, thousands of alerts about every component in your large scale distributed system is not what you want when the problem is one core router or switch that has failed. Letting through the significant alerts and suppressing alerts about consequential faults is a complex problem made easier by the better tools.
You also need to record enough information to be able to find the root cause from your logs.
The better tools allow you to automate response to select events. For example, restarting servers or services.
If you are concerned about security, you might also want indelible logs mirrored to one or more secure systems.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||