I am developing a large scale distributed system written in perl with multiple machines performing different data processing tasks. Modules crash from time to time and when they do, I write out their stacktrace to a log file. I later scan the log for crash patterns.
Is there a more reliable way (or even standard practice) of collecting bugs, filing and reporting them? I am looking for perl packages or software that can do the bug collection and processing tasks.
In particular I were to write one myself, what are some of the features a crash collection system should consider? My homegrown bug collector records the buggy input, stacktrace, machine etc. Upon hitting a bug the
module restarts on the next input and resumes processing.
Any advice would be much appreciated.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||