13.3.2 Designing monitoring

(1) Monitoring methods

Consider what elements in the system require monitoring, and in what way, to ensure that the system operates reliably.

System monitoring method:

In considering how the system is to be monitored, you must first analyze the elements that make up the system. Because a system can contain a broad range of elements, you can simplify the process by breaking down the system into a number of layers, such as those shown below, which can then be considered individually.

• Business: The types of jobs executed in the system

• Servers: The software and hardware components

• Network: The network configuration and the types of devices in the network

Next, consider the methods needed to monitor the various elements in the system. You could use a product designed for system management, for example. You could monitor routine business tasks based on information supplied by a job management server, or use tools designed to monitor applications running on a server, for example.

The products in the JP1 series support system operation from a variety of angles, delivering a total support package from system operation to monitoring.

Monitoring by JP1/IM:

JP1/IM manages the system using JP1 events.

Consider collecting the events occurring in the system as JP1 events by linking JP1/IM with the other programs that manage the various elements in the system.

You can collect JP1 events across the system by linking with the products in the JP1 series.

Messages and Windows event logs on the log file can be converted to JP1 events and managed by JP1/Base or JP1/IM-Agent.

It also manages the performance of your system by monitoring the performance of your JP1/IM-Agent.

To Page Top

(2) Monitoring targets

Consider what aspects or items you would need to monitor to ensure that the system is operating in a stable manner.

Monitoring targets:

Assess what sorts of items can be monitored by each monitoring method you considered earlier. For example, a JP1/IM-Agent performance monitoring can monitor the utilization and load on the resources it monitors.

Consider whether the items each product monitors are set appropriately for the local system. For example, check whether the threshold values defining the level at which resource usage triggers a JP1 event are at a suitable level.

JP1 events:

When you have settled on what items need to be monitored, consider how these items are recorded as values in JP1 events.

For products that issue JP1 events, ascertain how the item name and value are formatted in the JP1 event.

For log files, Windows event logs, or other events that are converted to JP1 events by a JP1/Base or JP1/IM-Agent, examine how the content of the original event corresponds to the information in the converted JP1 event.

To Page Top

(3) Monitoring viewpoints (when using the Central Scope)

If you wish to use the Central Scope, consider the viewpoints from which you need to monitor the system operation.

The Central Scope enables objective-oriented system monitoring matched to your monitoring viewpoints, and offers visual representation in a tree view in the Monitoring Tree window or map view in the Visual Monitoring window.

Monitoring tree:

The following monitoring trees can be generated using the auto-generation function:

• Work-oriented tree

• Server-oriented tree

You can then customize the tree to suit your needs by adding or deleting elements.

Visual monitoring:

You can arrange the key points that you want to watch closely in a map view using the Visual Monitoring window. Prepare the organizational charts or maps that you want to use as map images.

To Page Top