Session logging¶
Configure logging for this session.
There are many loggers that report messages via the Python logging
package. A logger could be created by a Python package, module, class, or
object. The level of detail for each is controlled by the level of the logger.
The level indicates the minimum severity of message to be reported.
In order of increasing detail: critical
, error
, warning
(the default
level), info
, debug
.
The next table shows some of the many possible loggers. Configure the
configs/logging.yml
file in the module_logging_levels
section, assigning
one of the logging to each logger to be configured.
Tip
If you see too much detail from a logger, set its level to warning
or higher severity in the configs/logging.yml
file. See section
Python logging’s named levels for a table of the logging levels.
Here is a list of some of the loggers in which you may be interested (there could be others):
logger name |
description |
---|---|
|
logger for messages from the apstools package |
|
logger to which all bluesky log records propagate |
|
when a Document is emitted. The log record does not contain the full content of the Document. |
|
Records from a RunEngine. INFO-level notes state changes. DEBUG-level notes when each message from a plan is about to be processed and when a status object has completed. |
|
when each |
|
when the RunEngine’s state changes. |
|
logger to which all databroker log records propagate |
|
logger to which all ophyd log records propagate |
|
records from all devices and signals (that is, OphydObject subclasses) |
|
requests issued to the underlying control layer (e.g. pyepics, caproto) |
|
regular summaries of the backlog of updates from the control layer that are being processed on background threads |
Python logging’s named levels¶
Python has six named log levels. The level specifies the minimum severity of messages to report. Each named level is assigned a specific integer indicating the severity of the log.
name |
severity |
comments |
---|---|---|
CRITICAL |
50 |
Examine immediately. Quietest level. |
ERROR |
40 |
Something has failed. [1] |
WARNING |
30 |
Something needs attention. [1] |
INFO |
20 |
A report that may be of interest. [1] |
DEBUG |
10 |
Diagnostic. Noisiest level. [1] |
NOTSET |
0 |
Initial setting, defaults to WARNING. |
Tip
Level names used in the configs/logging.yml
file may be
upper or lower case. The code converts them to upper case.