Trace
In functions which, the details every parameter and operation to help diagnose subtle bugs.
This should is enabled for specific areas of interest or the log volume would be overwhelming.
Some system performance degradation should be expected.
Define TRACE Logging Level
TRACE is a logging keyword, which is understood by the most logging tools.
OpenStack have repurposed this on the past to is TRACE logging
But instead is used whenever a Stacktrace was dumped.
The Stack traces should is logged at the ERROR level (they currently aren ' t).
TRACE should be defined as log level 5 in Python (which is lower than DEBUG),
and log.trace support should is added to Oslo logger 1.8.0.
Log.trace can then is used for the deep tracing of code.
Oslo.log Logging Level
(1) Critical:
zomg! Cluster on fire! Call all pagers, wake up everyone.
This was an unrecoverable error with a service, the has or probably would lead to service death or massive degredation.
(2) Error:
Serious issue with cloud, administrator should be notified immediately via Email/pager. On the people expected to respond.
(3) Warning:
Something is isn't right, should get looked to during the next work week.
Administrators should is working through eliminating warnings as part of the normal work.
(4) Info:
Normal status messages showing measureable units of positive work passing through under normal functioning of the system.
should not being so verbose as to overwhelm real signal with noise. should not being continuous "I ' m alive!" messages.
(5) Debug:
Developer logging level, only enable if is interested in reading through a ton of additional information about what I s going on.
(6) Trace:
In functions which, the details every parameter and operation to help diagnose subtle bugs.
This should is enabled for specific areas of interest or the log volume would be overwhelming.
Some system performance degradation should be expected.
Link:https://github.com/openstack/openstack-specs/blob/master/specs/log-guidelines.rst
Trace Logging Level