The Logs provide a set of tools dedicated to the tracking of information, error and debug messages. Their operation is similar to the alarm with extension mechanism (LogExt), of the classes to receive messages (LogGroup) and the receivers (LogReceiver, LogConsoleTool, etc.).
The Logs are very useful for tracking specific processes in a station: model modification, automatic element creation, logic, user modifications, etc. They are used automatically by btibStructure tools and can be enabled for certain btibTooIkit components.
Why use the logs system ?
The main advantage of the Logs is independence from the Application Director, which offers little functionality to filter logs, obtain more details about a log or store them long term. The alarms can play this role (filtering via alarm classes, export to different receivers...) but are generally used for other purposes (BMS alarms) and have low JACE capacity limits. On the other hand, the histories make it possible to monitor a value over the long term (and to benefit from filters) but are restricted to the monitoring of a single data source which makes it impossible to follow several sources in a single group.
The Logs combine operation of the alarms and the histories to offer greater flexibility in their use.
Architecture
The Log component located in the BtibService is dedicated to the management of the logs. It contains the LogGroup.
The Logs are sent by the LogExt to the LogGroups. The logGroups then forward the logs to the different recipients to which they are linked (LogRecipients and associated views, including the console).
Training
You can follow this e-learning course to practice
