Logging Levels

-
Most popular logging frameworks (e.g. Log4J, SLF4J, Log4Net, EntLib) allow for several logging levels to be instrumented. A common question is: What logging levels are appropriate under what scenarios? The following lists some common log levels are their usage:
  • Fatal -
    • Service/ application/ process about to terminate.
    • Unable to proceed with normal operation.
    • Force a shutdown to prevent (further) data loss.
    • Examples:
      • No more system resource (OOM)
  • Error -
    • Unhandled or unexpected system error has occurred.
    • Current operation/ thread to be aborted.
    • Issue needs to be fixed.
    • Still able to continue with normal operation (at least for other users/ sessions) otherwise.
    • Examples:
      • database deadlock
      • Unexpected/ unhandled exception
      • Runtime errors
      • Transaction aborted
      • Can't create file
  • Warn -
    • Things are generally working fine.
    • Recoverable conditions.
    • Transient environmental conditions happened.
    • Something happened (but was handled) that may potentially turn into error conditions soon but has yet to happen.
    • Examples:
      • number of connections getting low
      • operation timeout
      • CPU utilisation reaches 80%
      • data unavailable; using cached/ default values
  • Info -
    • Useful and important information for logging.
    • No cause for concern.
    • A normal & expected event happened.
    • Useful in the running and management of the system.
    • Examples:
      • Successful initialisation
      • Starting/ stopping of services
      • Successful transactions
  • Debug -
    • Useful in troubleshooting in production environment but otherwise, should only be used in development and testing environments.
    • Used by IT professionals (e.g. developers, system admins, etc.).
  • Trace -
    • Detailed tracing and logging.
    • Specifically for developers only.

Comments

Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

How to depict (Professional-Looking) Logical Network Diagrams in Astah

-
Image
I have always had to create (professional-looking) UML diagrams using Visio-like icons. You’ve got to admit that showing a bunch of boring UML boxes hardly interests anyone less technical (like anyone whose designation has the words “manager” or “director”). This is actually possible in Astah! I’ve created a template for future projects that allows me to produce logical network diagrams that look like the following: To create this diagram, you need to do the following: Assign various icons to stereotypes. I created the following for my use: Create a new UML Deployment Diagram Every element in the diagram is created as a Node The nodes are subsequently assigned the appropriate <<stereotype>>. E.g. Internet is <<internet>>, WebZone FW is <<firewall>>, Web LB is <<loadBalancer>> Ensure the “Icon Notation” is set to “Customized Icon” for each node Instead of the boring boxes, the corresponding icons automatically gets displayed!
Read more