The monitor is a named collection of IDS server performance parameters, related alert conditions, object filters and real-time graph definitions. The monitor is defined against a single IDS instance. You can select a subset from approximately one hundred available performance parameters defined at server, table/index, dbspace, chunk or session levels. For example, within one monitor definition, you can choose to monitor disk cache read percentage for entire server and number of requested locks for 10 most heavily used tables. For each selected parameter you can specify its own refresh interval, set the flag whether the parameter's data should be stored in the historical database for future analysis, enter optional alert conditions, and optionally choose to display a real-time graph for it. In case of table, chunk, space and session-level parameters, the data collection, alerting and graphing can be defined for each object separately. For example, for a TABLE BUFFREADS parameter you might want to record data only for 5 tables, set alert condition on 100 tables and graph in real-time only 2 most critical tables.
You can create multiple monitors for the same database instance in order to logically separate different database performance areas. Each monitor can be independently started and stopped. The group operations, such as starting and stopping of several monitors at once for the same or multiple IDS instances, are also supported.
All user-defined monitors' configurations are stored by the Sentinel server and are retrieved by Server Studio JE client when it connects to the Sentinel server.
If you need to apply similar monitors to several IDS instances, you can utilize the Replicate Monitor operation that allows you to use any existing monitor as a template for other database servers.
See Also: