Databases
StackOverflow2013
Postsdbo
POLogging vs. Debugging
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLogging vs. Debugging
    primarykey
    data
    text
    <p><strong>Background:</strong> I've inherited a web application that is intended to create on-the-fly connections between local and remote equipment. There are a tremendous number of moving parts recently: the app itself has changed significantly; the development toolchain was just updated; and both the local and remote equipment have been "modified" to support those changes.</p> <p>The bright side is that it has a reasonable logging system that will write debug messages to a file, and it will log to both the file and a real-time user screen. I have an opportunity to re-work the entire log/debug mechanism.</p> <p><strong>Examples:</strong></p> <ul> <li>All messages are time-stamped and prefixed with a severity level.</li> <li>Logs are for the customer. They record the system's responses to his/her requests.</li> <li>Any log that identifies a problem also suggests a solution.</li> <li>Debugs are for developers and Tech Support. They reveal the system internals.</li> <li>Debugs indicate the function and/or line that generated them.</li> <li>The customer can adjust the debug level on the fly to set the verbosity.</li> </ul> <p><strong>Question:</strong> What best practices have you used as a developer, or seen as a consumer, that generate useful logs and debugs?</p> <hr> <p><strong>Edit:</strong> Many helpful suggestions so far, thanks! To clarify: I'm more interested in <em>what</em> to log: content, format, <em>etc</em>.--and the reasons for doing so--than specific tools.</p> <p>What was it about the best logs you've seen that made them most helpful?</p> <p><em>Thanks for your help!</em></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAdam Liss
    1. USAdam Liss
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POLogging vs. Debugging
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POLogging vs. Debugging
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POLogging vs. Debugging
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload