Houdini’s logging system consists of sources and sinks. Sources generate and distribute log entries. Sinks receive log entries from sources, and do something with them. Sources are global, and identified by a unique name string (such as Node Errors
which is a source that generates a log entry for every message, warning, or error generated by nodes). There can be any number of sinks created in a Houdini session, and each one can connect to a different set of sources. Thus you could create one sink that sends all node errors to a file, another sink that sends all rendering messages to a different file, and a third sink that captures in memory all log entries generated by any sink (the same source may be connected to multiple sinks). This system allows for fine grained control over which log entries are captured, and what is done with each log entry.
API ¶
-
Represents a logging destination that writes log entries to a file.
-
Represents a single log message that is sent by a source to a sink.
-
Represents a logging destination that stores log entries in memory.
-
Represents a logging destination.
-
Create a new logging source which can send out log entries generated in python.
-
Return a shared file sink object owned by the current Houdini session.
-
Return a shared memory sink object owned by the current Houdini session.
-
hou.logging.loadLogsFromFile()
Load a tuple of LogEntry objects saved in JSON format from a file.
-
Send a LogEntry object to all log sinks connected to a logging source.
-
hou.logging.renderLogVerbosity()
Return the Karma logging verbosity level.
-
Save a tuple of LogEntry objects to a file in JSON format.
-
hou.logging.setRenderLogVerbosity()
Set the Karma logging verbosity level.
-
Return a tuple of all available log source names.