Log::Log4perl has these levels–

OFF   FATAL   ERROR   WARN   INFO   DEBUG   TRACE   ALL

[download]

In Catalyst/Log::Log4perl::Catalyst I just pick what makes sense at the time. Fatal and error both sort of define themselves. Warn is something important for the dev to see early and often until fixed. Info… seems a step too much but I have used it when waffling about using debug. Debug for normal, easy to understand flow information that is possible, or prone, to regressions/problems. Trace, the whole enchilada, too much really but some trouble shooting requires it. All… I don’t even think is supported in Catalyst logging… never saw it before tonight.

In reply to Re: Choosing a log level by Your Mother
in thread Choosing a log level by stevieb

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.