Just beware that, in some cases, sending an e-mail can be quite slow (and can slow down your application, if that matters), and, also, receiving too many e-mails leads to people just discarding them (or creating rules to send them to unwanted mails). You can log as many lines as you want through Log4Perl (although, here also, too much information might kill useful information), but receiving too many automatic emails is just a pain in the as*... hmm, well, in the neck. I get dozens of these automatic mails every day, I just no longer read them.

In reply to Re: Log to a file, but also log individual function to an email by Laurent_R
in thread Log to a file, but also log individual function to an email by Cagao

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.