5.2.3 Status change conditions

(1) Status change conditions for monitoring objects

The following figure shows status change conditions for monitoring objects.

Figure 5‒2: Status change conditions for monitoring objects

Each monitoring object in a monitoring tree has its own status change condition. When JP1/IM - Manager receives a JP1 event, it checks the status change condition of each object. If the condition is satisfied, and the status of the received event has higher priority than the object's current status, JP1/IM - Manager changes the object's status accordingly. In this way, generated JP1 events are associated with the relevant objects in the monitoring tree, providing a visual representation of the system status.

A status change condition for a monitoring object consists of a condition name, status, common condition, and individual conditions, as described below. Multiple common conditions and individual conditions can be specified for a JP1 event.

• Condition name

  The name of the status change condition.

• Status

  The status of the monitoring object when the status change condition is satisfied.

  One of the following can be specified: Emergency, Alert, Critical, Error, Warning, Normal, Debug, or Initial.

• Common condition

  A status change condition that applies to a number of monitoring objects. For example, for an object that monitors a jobnet, JP1 event ID 4108 (generated when a jobnet ends with a warning) is a common condition and applies to all such monitoring objects.

• Individual condition

  A condition whose value is specific to the object concerned. For example, a condition whose value changes for each monitoring object, such as the job name for a jobnet monitoring object, is an individual condition.

The following figure describes how a status change condition is set in practice, taking as an example a system-monitoring object.

Figure 5‒3: Example of a system-monitoring object (extract from "AJS Monitoring")

This figure is an extract from the description of the system-monitoring object called AJS Monitoring in Chapter 4. Lists of System-Monitoring Objects (for Central Scope) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

The example in the figure defines a status change condition with the title Jobnet warning event (AJS). As a common condition for all AJS Monitoring objects, the object status is set to Warning when event ID 4108 (indicating that the jobnet ended with a warning) is generated. As an individual condition set for each monitoring object, a condition related to the basic information held by the monitoring object (for identifying the object) identifies which of the objects in the monitoring tree changes its status.

In this way, a common condition related to the type of monitoring object (product name, for example) can be combined with an individual condition for identifying the specific monitoring object whose status will change.

Making status change conditions for monitoring objects resident in memory

When JP1/IM - Manager receives a JP1 event, it checks whether the status change condition of each monitoring object is satisfied. If a large number of JP1 events are received at once, the number of disk accesses increases accordingly and it could take longer to apply the new status to the monitoring objects. By making the status change conditions of the monitoring objects resident in memory, you can reduce the disk accesses during the Central Scope processing on receipt of an event.

When you use this functionality, the status change conditions for all monitoring objects are kept in memory. Sufficient memory is needed for this purpose. We recommend that you estimate the memory requirements and set up this functionality if sufficient memory can be allocated.

For the equations used when estimating memory requirements, see the Release Notes for JP1/IM - Manager. For details about how to set up this functionality, see 6.7.5 Setting the memory-resident status change condition function in the JP1/Integrated Management 2 - Manager Configuration Guide.

To Page Top

(2) Status change conditions for monitoring groups

A monitoring group is a set of monitoring nodes. Therefore, the status of the monitoring group changes according to the status of its constituent nodes. The following figure shows status change conditions for monitoring groups.

Figure 5‒4: Status change conditions for monitoring groups

When JP1/IM - Manager receives a specific JP1 event and changes the status of a monitoring object, the new status is passed to the higher-level monitoring groups. The default behavior is as follows.

Figure 5‒5: Status change behavior of a monitoring group (default setting)

As shown in the figure, the monitoring group status changes to the status that has highest priority among the lower-level monitoring nodes. Thus, when the topmost monitoring node has Error status, it means that none of the nodes under it has a status of higher priority than Error.

While the default settings are appropriate in most cases, more detailed monitoring can be performed by defining a status change condition for the monitoring group in special circumstances (such as a load-balancing system).

A status change condition for a monitoring group consists of a condition name, status, child node status, and comparison condition, as described below.

• Condition name

  The name of the status change condition.

• Status

  The status of the monitoring group when the status change condition is satisfied.

  In order of priority, the specifiable statuses are Emergency, Alert, Critical, Error, Warning, Normal, and Debug. Initial cannot be specified.

• Child node status

  The status of a lower-level monitoring node. Specify the status that will cause a change in the status of the monitoring group to which the node belongs. In order of priority, the specifiable statuses are Emergency, Alert, Critical, Error, Warning, Normal, and Debug. Initial cannot be specified.

  The status you specify here includes those of higher priority. For example, Error includes all statuses from Error upward.

  The following figure shows the child node concept.

  Figure 5‒6: Range of child nodes in a monitoring group

  As shown above, monitoring group B is included among the child nodes of monitoring group A, but its own child nodes are not included.

• Comparison condition

  A condition for comparing lower-level monitoring nodes within the group. You can specify a percentage (x% or higher) or a count (x nodes or higher), as follows.

  Figure 5‒7: Comparison conditions (percentage-based and count-based)

By setting a condition name, status, child node status, and comparison condition in this way, you can customize the conditions that cause the status of a monitoring group to change.

When you define a status change condition, the icon of the monitoring group changes as shown below. From the icon display you can tell whether a status change condition has been set for a particular group.

Figure 5‒8: Change in icon display (example)

"P" is not added to Visual Icon registered by the user. Identify whether a status change condition has been defined from the icons in the tree.

To Page Top