Logging in Operations Guide - TRACE

[Matt Riedemann]

This section talks about the TRACE log level:

http://docs.openstack.org/ops-guide/ops-logging.html#reading-the-logs

"OpenStack services use the standard logging levels, at increasing severity: DEBUG, INFO, AUDIT, WARNING, ERROR, CRITICAL, and TRACE. That is, messages only appear in the logs if they are more “severe” than the particular log level, with DEBUG allowing all log statements through. For example, TRACE is logged only if the software has a stack trace, while INFO is logged for every message including those that are only for information."

That makes it sound like TRACE > CRITICAL, but actually TRACE < DEBUG, see the logging guidelines here:

https://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html#definition-of-log-levels

The example here is also wrong:

"The first step in finding the source of an error is typically to search for a CRITICAL, TRACE, or ERROR message in the log starting at the bottom of the log file.

Here is an example of a CRITICAL log message, with the corresponding TRACE (Python traceback) immediately following:"

As of this change to oslo.log: https://review.openstack.org/#/c/166537/

Stacktraces are no longer use TRACE as the level, they are all ERROR, e.g.:

http://logs.openstack.org/40/365140/2/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/8c6013d/logs/screen-n-cpu.txt.gz?level=TRACE#_2016-09-06_15_27_35_424

http://paste.openstack.org/show/567250/

I'm not sure, however, to enable logging at TRACE level since we have the debug configuration option but we don't have something similar for trace that I can find.

-----------------------------------
Release: 0.0.1 on 2016-09-06 18:05
SHA: d56622b194607dfa04781ea03d38f9c127de7cbc
Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/ops-guide/source/ops-logging.rst
URL: http://docs.openstack.org/ops-guide/ops-logging.html

[Matt Riedemann (mriedem)]

I've filed an RFE bug with oslo.log to be able to configure and enable TRACE logging:

https://bugs.launchpad.net/oslo.log/+bug/1620789

[Lana (loquacity)]

That change has been abandoned, so I think we need to update the doc to reflect this behaviour.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/421383

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/421383
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=b338370d800a568c2acee5d0f5d826c65d7fdb85
Submitter: Jenkins
Branch: master

commit b338370d800a568c2acee5d0f5d826c65d7fdb85
Author: Alexandra Settle <email address hidden>
Date: Tue Jan 17 17:02:26 2017 +0000

    Correcting TRACE log level

    Change-Id: Ia74dfbd73dfcc265ee6bf5891ab628746d6d138d
    Closes-bug: 1620782

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.