Enabling self-monitoring

You can configure the Web GUI to record statistics about the responsiveness of the data source, the effectiveness of the cache that stores event data, and the utilization of the Java Virtual Memory (JVM). To enable this self-monitoring functionality, make changes to the data source definitions in the ncwDataSourceDefinitions.xml file.

When self-monitoring is enabled, system statistics are periodically checked. If a threshold breach is detected, an event is sent to the current primary ObjectServer that is defined in the data source. If information events are configured, an event is raised in the data source for each granularity period. The event contains the statistics that were gathered for the monitored system service. The following services are monitored

  • Data Source Command
  • Event Data Service
  • Event Summary Data Service
  • Metric Data Service
  • User and security repository
  • Results cache statistics
  • Java Virtual Memory utilization
  • Virtual Member Manager

When the thresholds for these services are breached, problem events of specified severities are raised in the data source. Default thresholds are provided. Optionally, an information event can also be raised. The events are always raised in the primary ObjectServer of the data source. The information event contains a summary of the monitored service. It has default severity of 2 (warning). The frequency with which the problem events and information events are raised is controlled by a granularity period setting. Information events have a configurable expiration setting. By default, this expiration period is the granularity period, plus 30 seconds. Self-monitoring is configured separately for each monitored service and for each data source.

Sample ncwDataSourceDefinitions.xml are in WEBGUI_HOME/dataources/samples. For an explanation of the elements that control self-monitoring, see Data source configuration file overview.

Before you begin

To generate self monitoring events you must apply the SQL customization before you configure self monitoring. This setup should be done for a standalone environment or a multitier environment. For more information on this and on creating or modifying data sources go to Creating or modifying data sources.

Procedure

  • Make a back-up copy of your current ncwDataSourceDefinitions.xml file.
  • To make the changes using the GUI complete the following steps:
    1. In the Web GUI console click the Administration icon and select Data Sources.
    2. Click either Modify Existing Data Source or Create New Data Source.
    3. In the Self Monitoring tab select the Enable Self Monitoring checkbox and change the thresholds and severities for the service as required using the relevant Configure Threshold buttons.
    4. Click Save Data Source.
  • To manually edit the xml file complete the following steps:
    1. Merge the <self-monitoring> elements from one of the sample XML files that are provided into your ncwDataSourceDefinitions.xml file.
    2. Enable self-monitoring by setting the <self-monitoring> element as follows: 
      <self-monitor enabled="false" granularity="300">
    3. Change the thresholds and severities for the service as required.
      Do not change the names of the services.
    4. Restart the server.

What to do next

Operators can now use the Netcool Health dashboard. The gauges at the top of the dashboard represent the services that are monitored. Events that are raised when thresholds are reached are displayed in the Event Viewer at the bottom.