Logging parameters
OIBus logs have five levels (from the most to the less critical):
- Error
- Warning
- Info
- Debug
- Trace
Activating Info logs will also activate Warning and Error logs. Activating Error logs will only display Error logs. Obviously, having Trace logs activated will result in extremely verbose logs. Use Trace and Debug for troubleshooting purposes.
Console
This section displays the logs in the Console, alongside values if a North Console connector is used.
File
To store logs in one or several files. You can choose the file maximum size and the number of files to roll logs.
SQLite
To store logs in a local SQLite database to be displayed in the Logs tab of OIBus.
Loki
To send the logs to a remote loki instance. Logs are sent to the specified host, in batches a tunable time period (default is 60s). You can change this period to have smaller or bigger batches of logs.
Loki can be accessed directly by username and password using Basic Auth. If a JWT token should be retrieved first, fill the Token address to use to retrieve the token, using Basic Auth (with the username and password). The token will be used by OIBus to send logs to the remote loki instance. Keep the token address empty if you don't use JWT token authentication.
Logs sent to loki are identified by the OIBus engine name. Be sure to update this name appropriately to find your OIBus logs in your loki instance.