Application Monitoring

The monitoring functionality in wRTOS allows you to trace the behavior of your real-time applications by recording significant events that occur during execution of those applications. The events are written to disk, where they are grouped into sessions. Each session corresponds to a single folder that contains one or more files containing events generated during that session. A new session begins each time monitoring is started, and the current session ends each time monitoring is stopped.

There are many kinds of events. For instance, one might represent the creation of a thread, another might represent a fast semaphore being acquired, and yet another might represent a thread exiting a critical section. Using the wRTOS Settings and wRTOS Monitor utility, you can choose the events you want to collect, filtering out the events that are of no interest. Events are stored in each session folder in binary form. Using wRTOS Monitor, you can convert a session file into text files showing the details of each event in the order in which the events happened.

Note: Monitoring causes as much as one microsecond of latency depending on the real time operation. It is recommended that you only enable and start monitoring during development and that you disable monitoring in production. The amount of latency depends on how many kinds of events are being monitored and how frequently those events occur in real-time applications. Monitoring fewer kinds of events reduces the impact of monitoring on latency.

Configuring Default Monitoring Settings

In wRTOS Settings, you can specify the global, persistent default monitoring settings you want to use when the Subsystem is started.

For example, you can:

Note: You can configure the overall amount of non-paged memory that the Subsystem will dedicate to collecting monitored events through the Memory Settings page in wRTOS Settings.

Controlling Monitoring Sessions

Once monitoring is enabled in the wRTOS Settings, you can use wRTOS Monitor to:

Related Topics: