25.01.2015 Views

Caché Monitoring Guide - InterSystems Documentation

Caché Monitoring Guide - InterSystems Documentation

Caché Monitoring Guide - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Using the <strong>Caché</strong> Monitor<br />

3.2 <strong>Caché</strong> Application Monitor<br />

The <strong>Caché</strong> Application Monitor (Application Monitor) monitors system- and user-defined metrics. It is an extendable <strong>Caché</strong><br />

utility that monitors the system for performance and system data, generates alerts, handles notifications, and generates and<br />

maintains a persistent repository of all such data. It is a modular system that allows instances of the monitor to run in multiple<br />

namespaces concurrently. Each instance of the Application Monitor lets you do the following in each namespace in<br />

which it is activated:<br />

1. Register system classes in the local namespace.<br />

2. Activate the system- and user-defined classes you want to monitor. For user-defined classes, you can activate only<br />

those classes that you have created in the local namespace; that is, if you created a user-defined class in the USER<br />

namespace, you can only activate that user-defined class in the USER namespace.<br />

3. Start an instance of the Application Monitor (%MONAPP) in the local namespace. When an Application Monitor is<br />

started in a local namespace, it searches for all classes that have been activated and, for each activated class, it creates<br />

sample data in local namespace globals. Monitor metadata is kept in globals ^ISCMonitor():<br />

^ISCMonitor("Monitor","AppInterval")=300<br />

^ISCMonitor("Monitor","Interval")=10<br />

^ISCMonitor("Monitor","Metric","%Monitor.System.Dashboard","Active")=1<br />

^ISCMonitor("Monitor","Recipients")=""<br />

^ISCMonitor("Monitor","SmtpServer")=""<br />

Sample data is kept as persistent data for the sample class. You may view this data by invoking class methods, or via<br />

a browser; all sample classes are automatically CSP-enabled.<br />

This section discusses the following topics:<br />

• Application Monitor Manager – information about managing the Application Monitor<br />

• <strong>Caché</strong> Metrics – information about system-defined metrics<br />

• Writing User-defined Monitor Classes – information about writing user-defined monitor classes<br />

3.2.1 Application Monitor Manager<br />

The Application Monitor Manager (^%MONAPPMGR) is an interactive utility that lets you perform Application Monitor<br />

management functions. Instances of the Application Monitor Manager can be executed in multiple namespaces concurrently<br />

with different parameters for each namespace, which enables multiple Application Monitors, each with its own activated<br />

classes and notification options, to run simultaneously; the name of the utility is case-sensitive.<br />

1. To start the Application Monitor Manager, enter the following command in the <strong>Caché</strong> Terminal:<br />

USER>do ^%MONAPPMGR<br />

2. The main menu appears. Enter the number of your choice or press Enter to exit the Application Monitor Manager:<br />

1) Manage Application Monitor<br />

2) Manage Monitor Classes<br />

3) Change Default Notification Method<br />

4) Manage Email Options<br />

5) Manage Alerts<br />

6) Exit<br />

Option<br />

The options in the main menu let you manage the Application Monitor as described in the following table:<br />

22 <strong>Caché</strong> <strong>Monitoring</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!