The ^%SYSMONMGR utility lets you manage and configure the System Monitor. The utility can be executed in any namespace, and changes made with it affect only the namespace in which it is started. You must maintain a separate System Monitor configuration for each startup namespace you configure by starting ^%SYSMONMGR in that namespace. Fol-lowing any change you make to the System Monitor configuration for a namespace, you must restart System Monitor in the namespace for the change to take effect.
To manage the System Monitor, enter the following command in the Caché Terminal:
%SYS> do ^%SYSMONMGR
The main menu appears.
1) Start/Stop System Monitor 2) Set System Monitor Options 3) Configure System Monitor Classes 4) View System Monitor State 5) Manage Health Monitor 6) Manage Application Monitor 7) Exit
Option?
Enter the number of your choice or press Enter to exit the utility.
Remember that con
The options in the main menu let you perform System Monitor tasks as described in the following table:
Description
• Set the sampling interval for configured sensor classes
• Set the debugging level of information written to the System Monitor log
• Return default sampling interval and debugging level to their defaults
3) Configure System Monitor Components
• Configure or remove user-defined sensor, subscriber and notifier classes
• Configure startup namespaces
4) View System Monitor State
• Display the operating status of System Monitor and its configured components
5) Manage Application Monitor
• Display the Application Monitor submenu
6) Manage Health Monitor
• Display the Health Monitor submenu
4.1.4.1 Start/Stop System Monitor
When a Caché instance starts, System Monitor starts automatically and begins calling configured classes in each configured startup namespace; this cannot be changed. While the instance is running, however, you can stop System Monitor, and must do so in order to change the configuration of Caché Health Monitor. In addition, following any change you make to the System Monitor or Application Monitor configuration for a namespace, you must restart System Monitor in the namespace for the change to take effect.
When you enter 1 at the main menu, the following menu is displayed:
1) Start System Monitor 2) Stop System Monitor 3) Exit
Enter 2 to stop System Monitor when it is running, and 1 to start it when it is stopped.
4.1.4.2 Set System Monitor Options
1) Set Sample Interval 2) Set Debugging Level 3) Reset Defaults 4) Exit
Enter 1 to set the interval at which System Monitor calls each configured sensor class; the default is 30 seconds.
Enter 2 to set the debugging level. The default is 0 (base) which writes basic messages, error messages, and Health Monitor alerts and warnings to the System Monitor log; 1 (log all sensors) writes sensor readings as well.
Enter 3 to reset the sample interval and debugging level to their defaults.
Your changes take effect when you next start System Monitor.
4.1.4.3 Configure System Monitor Components
As described in Caché System Monitor Process, you can create your own sensor, subscriber and notifier classes by extending %SYS.Monitor.AbstractSensor, %SYS.Monitor.AbstractSubscriber, and %SYS.Monitor.AbstractNotification, respectively, and configure them in System Monitor to extend the capabilities of the provided classes described in Default System Monitor Classes. You can also add namespaces other than %SYS for System Monitor to start and run in.
Configure System Monitor Classes
When you enter 3 at the main menu, the following menu is displayed:
1) Configure Components
2) Configure Startup Namespaces 3) Exit
Enter 1 to display the options for configuring classes:
1) List Classes 2) Add Class 3) Delete Class 4) Exit
Enter 1 to list the currently configured classes for the namespace in which you started ^%SYSMONMGR, including provided system classes and those you have configured.
Enter 2 to configure a user-defined class for the namespace in which you started ^%SYSMONMGR. The class you specify must exist in the namespace and be recognized by System Monitor as a valid sensor, subscriber or notifier class.
You can also enter a description of the class.
Enter 3 to delete a user-defined class you have configured.
Note: Configuring or deleting a class affects only the namespace in which you started ^%SYSMONMGR.
Configure System Monitor Namespaces
When an instance starts, System Monitor automatically starts as a separate process in each configured startup namespace (by default %SYS only). All System Monitor configurations and settings are namespace-specific. When you make changes using ^%SYSMONMGR, the changes affect only the namespace in which you started the utility.
Note: All instances of ^%SYSMONMGR write messages to the same System Monitor log. Startup namespaces can be configured from any namespace.
When you enter 3 at the main menu, the following menu is displayed:
1) Configure Components
2) Configure Startup Namespaces 3) Exit
Enter 1 to display the options for configuring namespaces:
1) List Startup Namespaces 2) Add Namespace
3) Delete Namespace 4) Exit
Enter 1 to list the currently configured startup namespaces.
Enter 2 to add a startup namespace.
Enter 3 to delete a startup namespace. (You cannot delete %SYS.)
4.1.4.4 View System Monitor State
Enter 4 at the main menu to display the status of System Monitor and its components in the namespace in which you started
^%SYSMONMGR, for example:
Component State System Monitor OK
%SYS.Monitor.AppMonSensor None SYS.Monitor.SystemSensors OK
SYS.Monitor.Health.Control Running: Period is Thursday 09:00 - 11:30 SYS.Monitor.SystemSubscriber OK
SYS.Monitor.SystemNotifier OK
In this example, System Monitor and its system sensor, subscriber and notifier classes are running normally, as is Health Monitor’s subscriber class. However, none of Application Monitor’s classes are activated (see Manage Monitor Classes), so it is not evaluating sensor samples or generating alerts.
4.1.4.5 Manage Application Monitor
See Using ^%SYSMONMGR to Manage Application Monitor.
4.1.4.6 Manage Health Monitor
See Using ^%SYSMONMGR to Manage Health Monitor.