Logging

Logging is useful during Skill development, as well as to help end-users diagnose problems in the future.

To track events and data within your Skill we can use logging. If you are new to programming, this is a way to output a message that can tell you the state of your Skill at a particular point in time, details about an error that has occured, or simply noting that a program reached a particular point in the code.
Video Tutorial
Video Tutorial: Logging from Mycroft Skills
Basic Usage
A logger is available through the MycroftSkill base class. This means that you can use it within a Skill without needing to import the logging package. You can simply call self.log from within the class of your Skill.
Here is a quick example of an INFO level log message used in a Skill. We will learn more about the other levels shortly.
from adapt.intent import IntentBuilder
from mycroft import MycroftSkill, intent_handler
​
class LoggingSkill(MycroftSkill):
​
    @intent_handler(IntentBuilder('HelloWorldIntent')
                    .require('HelloWorld'))
    def handle_hello_world_intent(self, message):
        """ Skills can log useful information. These will appear in the CLI and
        the skills.log file."""
        self.log.info("This is an info level log message.")
        self.speak_dialog("hello.world")
​
def create_skill():
    return LoggingSkill()
What is included in a log message?
The above Skill would log an INFO level message each time the intent handler was triggered. The resulting log would look like this:
2021-03-19 16:06:43.731 | INFO     | 14745 | HelloWorldSkill | This is an info level log message.
From left to right, this consists of:
A timestamp identifying when the log was emitted.
The level of the log message
The Process ID (PID) of the system process where the log originated.
The origin of the log from within Mycroft. In the case of Skills the Class name is used.
The log message passed as an argument to the logger.
Where do these messages get logged?
Log messages from a Skill are displayed in the Mycroft CLI so that a User can see in real-time what is happening in the Skill. They are also written to the skills.log file located at: /var/log/mycroft/skills.log
By default all INFO, WARNING, ERROR, EXCEPTION and CRITICAL level messages will be logged. DEBUG level messages will be logged if the User explicitly requests it. This can be done by issuing the :log level debug command in the CLI, or changing the log_level attribute in the mycroft configuration.
When you first turn on DEBUG level logging, you will quickly notice that there is a lot happening behind the scenes in Mycroft. If you are debugging a particular Skill it is very useful to limit the displayed log messages using the Class name of your Skill. For the HelloWorldSkill we would use the CLI command: :find HelloWorldSkill
Finally to return to the default INFO level logging, you can issue the :log level info CLI command.
Logging Levels
There are five types of log messages available that are used for different purposes.
DEBUG
self.log.debug()
Debug messages are used for information that will help to diagnose problems. These are particularly useful if there is anything that has the potential to break in the future.
By default these messages will not be logged unless the User has explicitly turned on debug level logging.
INFO
self.log.info()
Info messages provide general information when the Skill is running as expected. These messages will always be logged so are useful when actively developing a Skill. When preparing to publish a Skill to the Marketplace, you will likely want to convert many of these to the DEBUG level.
WARNING
self.log.warning()
Warning messages are used to indicate that something has gone wrong, but the Skill will continue to function.
ERROR
self.log.error()
Error messages indicate that a serious problem has occured and the Skill will not be able to function. In the Mycroft CLI these messages are shown in red to make them highly visible.
EXCEPTION
self.log.exception()
Exception messages are an extended form of the error level message. These messages include a stack trace and should only be called from an exception handler. For example:
try:
    1/0
except ZeroDivisionError as e:
    self.log.exception("Cannot divide by zero")
CRITICAL
self.log.critical()
A more serious error, indicating that the Skill is unable to continue running.
Using the logger outside the Skill class
As the logger is provided by the MycroftSkill class, it is only available within that scope. If you need to log messages from outside of this class, you can import the logger manually.
from mycroft.util import LOG
This can then be used outside your Skill's class. Extending our first example:
from adapt.intent import IntentBuilder
from mycroft import MycroftSkill, intent_handler
from mycroft.util import LOG
​
LOG.info("This is a logged info level message outside of the MycroftSkill Class scope")
​
def my_special_function():
  LOG.info("Another usage of LOG.")
​
class LoggingSkill(MycroftSkill):
​
    @intent_handler(IntentBuilder('HelloWorldIntent')
                    .require('HelloWorld'))
    def handle_hello_world_intent(self, message):
        """ Skills can log useful information. These will appear in the CLI and
        the skills.log file."""
        self.log.info("This is an info level log message.")
        self.speak_dialog("hello.world")
        my_special_function()
​
def create_skill():
    return LoggingSkill()

Lifecycle Methods

Skill Settings

Last modified 1yr ago