lenskit.logging.monitor#

LensKit background monitoring.

Code almost never needs to interact directly with the monitoring subsystem.

Functions

get_monitor()

Get the monitor, starting it if it is not yet running.

Classes

`Monitor`()	LensKit monitor controller.
`MonitorRefreshable`(args, *kwargs)
`MonitorState`(value[, names, module, ...])
`MonitorThread`(monitor, log_sock)	LensKit monitoring backend thread.

class lenskit.logging.monitor.MonitorRefreshable(*args, **kwargs)#

Bases: Protocol

monitor_refresh()#: Refresh this object in response to monitor refresh timeouts.

lenskit.logging.monitor.get_monitor()#

Get the monitor, starting it if it is not yet running.

Return type:: Monitor

class lenskit.logging.monitor.MonitorState(value, names=<not given>, *values, module=None, qualname=None, type=None, start=1, boundary=None)#: Bases: Enum

class lenskit.logging.monitor.Monitor#

Bases: object

LensKit monitor controller.

The monitor does several things:

Receive and re-inject log messages from worker processes.
Track work in progress and periodically write work logs.

The monitor is managed and used internally, and neither LensKit client code nor component implementations often need to interact with it.

class lenskit.logging.monitor.MonitorThread(monitor, log_sock)#

Bases: Thread

LensKit monitoring backend thread.

Parameters:

monitor (Monitor)
log_sock (Socket[bytes])

run()#

Method representing the thread’s activity.

You may override this method in a subclass. The standard run() method invokes the callable object passed to the object’s constructor as the target argument, if any, with sequential and keyword arguments taken from the args and kwargs arguments, respectively.

Return type:: None