OpenHAB
/
openhab-docs
mirror of https://github.com/openhab/openhab-docs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
openhab-docs/administration/logging.md

5.2 KiB
Raw Blame History

layout
documentation

{% include base.html %}

Logging in openHAB

This chapter describes the logging functionality in openHAB:

Looking at the log

There are two ways to check log entries:

  1. In the log file stored in the file system
  2. During runtime in the Karaf console

File System

Log files are written to the directory userdata/logs an can be accessed using standard OS tools for text files. The default installation of openHAB generates two log files:

  • events.log
  • openhab.log

Karaf console

The Karaf console allows to monitor the log in realtime.

The log shell comes with the following commands:

  • log:clear: clear the log
  • log:display: display the last log entries
  • log:display-exception: display the last exception from the log
  • log:get: show the log levels
  • log:set: set the log levels
  • log:tail: continuous display of the log entries

For example, following command enables the realtime monitoring of the default log:

openhab> log:tail
12:45:23.170 [INFO ] [marthome.event.ItemStateChangedEvent] - Sonos_Kueche_Controller changed from PLAY to PAUSE
14:29:52.648 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'hue:PAR16_50_TW:1:24' changed from ONLINE to OFFLINE: Bridge reports light as not reachable
14:29:76.348 [DEBUG] [ipse.smarthome.model.script.JK.Sonos] - This is a debug message!

An useful functionality is that also filters can be applied:

openhab> log:tail org.eclipse.smarthome.model.script.JK
14:29:76.348 [DEBUG] [ipse.smarthome.model.script.JK.Sonos] - This is a debug message!

Please see the Karaf documentation for more examples and details.

Defining what to log

In order to see the messages, logging needs to activated defining what should be logged and in which detail. This can be done in Karaf using the following console command:

log:set LEVEL package.subpackage

The what is defined by package.subpackage and is in most cases a binding (like org.openhab.binding.sonos)

The detail of logging is defined by one of the following levels:

  1. Error
  2. Warn
  3. Info
  4. Debug

The levels built a hierarchy with Error on the top and Debug on the bottom. So when setting the log level to Debug, all logs from levels 1-4 are shown.

Following example sets the logging for the SONOS binding to Debug

log:set DEBUG org.openhab.binding.sonos

Note that the log levels set using the log:set commands are not persistent and will be lost upon restart. To configure those in a persistent way, the commands have to be added to the configuration file.

Create log entries in own rules

It is also possible to create own log entries in rules. This is especially useful for debugging purposes.

For each log level there is an corresponding command for creating log entries. These commands require two parameters: the subpackage (here: JK) and the text which should appear in the log:

logError("JK","This is a log entry of type Error!")
logWarn("JK","This is a log entry of type Warn!")
logInfo("JK","This is a log entry of type Info!")
logDebug("JK","This is a log entry of type Debug!")

In order to see the messages, logging for the message class has to be activated. The main package is predefined (org.eclipse.smarthome.model.script) and the subpackage needs to be concatenated:

log:set DEBUG org.eclipse.smarthome.model.script.JK

The output for the above log statement of type Debug is:

2016-06-04 16:28:39.482 [DEBUG] [.eclipse.smarthome.model.script.JK] - This is a log entry of type DEBUG!

Logging into a separate file

Per default all log entries are saved in the file openhab.log and event specific entries also in the file events.log. Additional files can be defined in order to write specifics logs to a separate place.

In order to create a new log file following two areas needs to be added to the config file:

  1. A new file appender:
# File appender - jk.log
log4j.appender.jk=org.apache.log4j.RollingFileAppender
log4j.appender.jk.layout=org.apache.log4j.PatternLayout
log4j.appender.jk.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n
log4j.appender.jk.file=${openhab.logdir}/jk.log
log4j.appender.jk.append=true
log4j.appender.jk.maxFileSize=10MB
log4j.appender.jk.maxBackupIndex=10
  1. A new logger:
# Logger - jk.log
log4j.logger.org.eclipse.smarthome.model.script.JK = WARN, jk
log4j.logger.org.eclipse.smarthome.model.script.JK.Sonos = DEBUG

Config file

The config file for logging is org.ops4j.pax.logging.cfg and can be found in the runtime/karaf/etc/ folder (in case openHAB was installed via apt, the full path is: /usr/share/openhab2/runtime/karaf/etc/)

Note: Currently the file org.ops4j.pax.logging.cfg will get overwritten with the default version on every update of openHAB. There is an issue on this.