Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
One I don't see mentioned is "logging to stop arguments!"

From a corporate point of view logging can be very helpful. A few scenarios:

  1. Customer calls to complain about delivery of something ordered on our web-store (true story). With the appropriate logs we can tell him exactly what happened at each step of the process and when. For one client of mine this saved a rather large order (10's of thousands of dollars). An employee of the purchaser had not ordered goods when he was supposed to. His boss called to complain and cancel. When he was given the facts he did not cancel, thanked everyone for their assistance and has been a regular repeat client ever since.
  2. "I never got that email!" roars the unsatisfied client. Just go parse your mail logs!
  3. Employee 'A' gets reamed out by supervisor for not following established procedure. Logs eventually tell us that while 'A' had read the latest revision to the online procedure manual his supervisor hadn't.
And I could go on. Logging in fact has far more uses than just those tied up with IT. For debugging and testing they are essential. But developers should think more about how logs can be used to make other aspects - particularly audit trail and change tracking much easier.

jdtoronto


In reply to Re: When to use logging and why? by jdtoronto
in thread When to use logging and why? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others surveying the Monastery: (3)
As of 2024-03-28 17:17 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found