Event Logging

ISys Event Logging Feature List

Lextel’s ISys Event Logging System for use in Embedded and Real Time systems provides a software library and API that makes it easy to generate, distribute, store, and analyze events generated while a system is running. The features in the ISys Event Logging System save countless man-hours during development and deployment of embedded applications and products.

High Level API

Events are specified and registered with the system using a simple C++ API. Events are generated while a system is running using a single ‘log’ function call.

Client/Server Design

Events are generated from user tasks as ‘clients’, and are sent to one or more log ‘server’ tasks running on the same, or other processors.

The events are forwarded to the log server tasks ‘in the background’, allowing the user task to continue running without waiting for the event to be transmitted to the log server tasks.


Filters can be applied to log servers, such that only events of interest are forwarded to those log servers. The filtering is performed at the client end, thus reducing communications overhead.

Filters can be specified on a number of criteria, including message priority, message source processor, message source software component, and others.

Extensible Log Server Actions

Log Servers are designed to take specific actions on receipt of event log messages. For example, log servers provided with the base system support output of log messages to consoles in human readable format, and storage of log messages to disc data base files.

The programmer can easily create custom log servers that perform other actions, such as turning on audible and visible alarms, sending snmp traps, sending email to a system administrator, or enabling a backup system.

Prioritization and Other Common Information

Log Messages contain priority information, as well as other common information such as time of generation, generating processor, and generating software component.

File Storage and Query

The built in Log Server for Disc Storage stores received log messages in data base files. Various controls are provided for specifying the maximum size of the files, when to close out and open files ( i.e. based on date, or size ), how to name the files, where to store the files, etc.

CLI Commands are available for querying the stored log files based on various criteria.

Log information is stored in the data base files in a way that minimizes the storage requirements.

Log System Control

Control for the event logging system is performed either by the programmer, or via built in CLI commands. For example, CLI commands are provided to add and remove filters from log servers, to display the contents of log files, etc.

Distributed Processing

Log Servers and the clients generating log messages may be located on separate, physically distant processors. The only requirement is that ip communications between them is available.

(Back to Embedded Systems Middleware)

Comments are closed