Regarding the Nagios approach, you could have your program log errors to file, then use Nagios to monitor the file - possibly using the check_logs plugin
If you're concerned about your programs terminating unexpectedly, you could either:
- do some basic monitoring to see if the process is still running (for long-running processes), or
- log a 'program starting' message, then write a plugin to check for subsequent 'in progress' messages (or a corresponding 'program finishing' message) within a certain time period, and raise an alert if you've not heard anything.
That would be the stuff that's most applicable to your situation as I understand it - there are plugins for an awful lot of sysadmin-related tasks, so I guess your use of Nagios is going to be dictated by how much of the other functionality is going to be of use. If your sole use is going to be for monitoring your own code, installing and configuring Nagios is probably going to be overkill. Still, it's nice to have options, eh? ;-)
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.