Change the monitoring level for a session or service

You can manage the amount of detail written to your monitoring data (.dat) files for a session or service.

The monitoring level sets the level of detail written to the monitoring data (.dat) files for a session or service. By default, the level is set to the minimum (MIN*), which means that only events raised by alarms are written.

Table 1. Monitoring levels
Level Description
ALARM Only alarms are raised. No data is recorded in the monitor files.
MIN* (Default) Alarms are raised and only the alarm events are store in the dat file.
MEDIUM Alarms are raised, alarm events and average time computations are stored in the dat file.
HIGH Alarms are raised, alarm events, average time, and real time computations are stored in the dat file. This provides you with more detail about the frequency of events in order to detect an abnormal event when debugging.

Raise or lower the monitoring level to meet your requirements. For example, raising the monitor level to the highest level (HIGH) can be useful when you want to debug.

gasadmin commands

To set the monitoring level on a session, for example:

  • gasadmin monitoring update --level HIGH --session d98290172c8f7c0d861db329f1ce6597

    The session must be running. The configuration takes effect immediately.

To set the monitoring level on a service, for example:

  • gasadmin monitoring update --level HIGH --service demo/Calculator

    You can set the monitoring level on a service that is not running. The configuration takes effect the next time the service is started.