8.2.8 Selection of agent configuration or remote monitoring configuration
Using IM Configuration Management, you can use JP1/Base to monitor hosts in agent configuration, or remotely monitor hosts in a remote monitoring configuration.
In remote monitoring, a communication failure related to functional errors might cause log monitoring to stop or events to be lost. If the system cannot tolerate temporary stoppage of log monitoring, install JP1/Base and use it for log monitoring.
In both the agent configuration and remote monitoring configuration, multiple manager hosts cannot monitor one host.
Use the following table to help decide whether to use monitoring using JP1/Base or remote monitoring.
Item |
Monitoring using JP1/Base |
Remote monitoring |
---|---|---|
You perform monitoring that exceeds the restrictions for remote monitoring. |
Y |
N |
The stoppage of log monitoring and loss of events is undesirable in the system.#1 |
Y |
N |
Log monitoring is required even while JP1/IM - Manager is stopped. |
Y |
Y#2 |
Monitored hosts are frequently stopped. |
Y |
N |
WMI/NetBIOS (NetBIOS over TCP/IP) or SSH cannot be used on the system.#3 |
Y |
N |
Multiplexed monitoring.#4 |
Y |
N |
Other than above. |
Y |
Y |
- Legend:
-
Y: Monitoring is performed.
N: Monitoring is not performed.
#1: When monitoring using JP1/Base, if a network failure occurs, JP1/Base acquires logs during the network failure. With remote monitoring, the monitoring stops if the failure cannot be recovered by retrying the operation.
#2: Not trapped if the event that occurred during the stop period exceeds the maximum size that can be collected by remote monitoring.
#3: With remote monitoring, settings for remote communication must be configured on the host on which JP1/IM - Manager has been installed and on the monitored hosts. The communication method depends on the OS of the monitored host. WMI/NetBIOS (NetBIOS over TCP/IP) must be configured if the monitored host is a Windows host, or SSH must be configured if the monitored host is a UNIX host.
#4: Multiplexed monitoring indicates that JP1 events are monitored by managers in both the primary and secondary systems. This is done by transferring JP1 events that occurred in a monitored host to the manager hosts in both the primary and secondary systems.
For details about remote monitoring, see 8.6 Managing remotely monitored hosts.
Some limitations apply to remote monitoring. For the limit values, see the following table.
Item |
Limit |
---|---|
Maximum number of remote monitoring units#1 |
1,024 |
Maximum size of the log files that can be remotely monitored |
64 MB |
Maximum amount of log data that can be collected per monitoring interval (Windows)#2 |
10 KB#4 |
Maximum amount of log data that can be collected per monitoring interval (UNIX)#2 |
10 KB#4 |
Maximum amount of event log data that can be collected per monitoring interval#3 |
10 KB#4 |
Maximum amount of log data that can be collected by one JP1/IM - Manager |
10 MB |
#1: Total value of the number of log files monitored by remote log file trapping and the number of servers monitored by remote event-log trapping
#2: Total size of log data collected.
#3: Total size of Windows event log data collected.
#4: Default value. This limit value can be changed in the remote log trap environment definition file (jp1cf_remote_logtrap.conf). For details about the remote log trap environment definition file (jp1cf_remote_logtrap.conf), see Remote log trap environment definition file (jp1cf_remote_logtrap.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
- Organization of this subsection
(1) Functional differences between the agent configuration and the remote monitoring configuration
Item |
Agent configuration |
Remote monitoring configuration |
---|---|---|
Use |
|
When reducing load in the construction of an environment and for other operations has priority over monitoring accuracy#1 |
Monitored logs and file formats |
|
|
Scale |
|
|
Event issued |
|
|
Size of log files that can be monitored |
2 gigabytes or less |
64 megabytes or less |
Size of log data that can be collected during a monitoring interval |
Unlimited |
In Windows: 200 kilobytes or less In UNIX: 50 kilobytes or less |
Maximum size of event log that can be collected per monitoring interval |
Unlimited |
200 kilobytes or less |
Log file trap start option |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In Windows, Unicode can be specified. |
Various character encodings that can be specified for the OS. |
|
|
|
|
|
|
|
Log file trap action definition |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Event log trap action definition |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Operation when manager stops |
If the manager host stops or a network failure occurs between the manager host and a monitored host, an agent host can convert the event into a JP1 event, and retry transfer of the generated JP1 event to the manager host. |
The log files and Windows event logs generated while JP1/IM - Manager is stopped are trapped the next time remote monitoring is started. |
Operation when network fails |
If network operation is restored after a failure before the maximum number of retries is reached and monitoring stops, the manager host will be notified of the log data collected during the failure period. Notification will be done only when none of the following restrictive conditions exist:
|
|
Host name |
A host name registered in the hosts file or DNS or a host name defined in jp1hosts or jp1hosts2 is specified for a host name. |
A host name registered in the hosts file or DNS is specified for a host name. The settings of jp1hosts and jp1hosts2 are not referenced. |
#1: If the amount of log data output during the monitoring interval exceeds this limit value in UTF-8, JP1 events cannot be displayed in JP1/IM - View. If this is a possibility, consider using log monitoring in an agent configuration. For details about the limit values, see Table 8-17 Limit values for remote monitoring.
#2: When IM Configuration Management is used, the maximum number of log file traps that can be managed is 100 for each agent host.
#3: Can be specified only if the agent's JP1/Base version is 10-00 or later.
#4: The default value is 10 kilobytes. This limit value can be changed in the remote log trap environment definition file (jp1cf_remote_logtrap.conf). For details about the remote log trap environment definition file (jp1cf_remote_logtrap.conf), see Remote log trap environment definition file (jp1cf_remote_logtrap.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
For details about each function in an agent configuration, see the documentation for the JP1/Base version that is installed on the monitoring target.