In the course of developing, debugging information is invaluable. But there are times when I don't want to see every possible debug message. So this requires debug levels. My question is: what guidelines you have used for determining what is logged at each debug level? I've been using numeric levels, with increasing numbers logging more data. The other end of the spectrum involves the use of text levels, such as "debug", "warning", "emergency". I'm leaning towards keeping numeric levels. But I'm interested in what other mongers have used. The issue is still open, so please convince me if you think your idea is better.
As for the actual logging mechanism, I plan to use Log::Dispatch::Config. It seems quite flexible and well designed. Flexibility is key, because on my home server I have access to the error log, while on my shared production host I have very limited access so a seperate file is easier. Thanks for all your ideas.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|