8.6.9 Precautions when remotely monitoring log files or event logs
- Organization of this subsection
-
-
(2) Precautions for the IM host account of the System Common Settings
-
(3) Precautions on the package required for the monitoring target host
-
(4) Precautions on using a version of OpenSSH earlier than OpenSSH 4.6p1
-
(5) Precautions on remote monitoring with JP1/IM - Manager in a cluster environment
-
(6) Precautions on name resolution of the target host of remote monitoring
(1) Review technical information for remote monitoring
Windows Remote Monitoring uses the WMI function of Windows OS. Therefore, it operates according to WMI specifications. WMI specifications may be updated, so please check the following for information before use.
http://support.microsoft.com/
(2) Precautions for the IM host account of the System Common Settings
If the host of JP1/IM - Manager is Windows Server 2012, Windows Server 2012 R2, or Windows Server 2016, Windows Server 2019, or Windows Server 2022,specify either of the following as the IM host account.
-
If the UAC functionality is enabled:
Built-in administrator of the JP1/IM - Manager host
-
If the UAC functionality is disabled:
The user who belongs to the administrator group of the JP1/IM - Manager host
# For Windows Server 2012, Windows Server2012 R2, Windows Server 2016, Windows Server 2019 or Windows Server 2022, you must disable User Account Control: Run all administrators in Admin Approval Mode in the Local Security policy.
Please check with your operating system for the impact of changes to the local security policy. After changing the IM host account settings, restart the JP1/IM - Manager service.
(3) Precautions on the package required for the monitoring target host
To collect log data, the package is required. Refer to the Release Notes and apply the required package.
(4) Precautions on using a version of OpenSSH earlier than OpenSSH 4.6p1
If you use a version of OpenSSH earlier than OpenSSH 4.6p1, the following error might be output in the system log of the monitoring target host. However, this error does not affect the operation of JP1/IM - Manager.
System log that is output
error: channel 0: chan_read_failed for istate 3
To prevent output of this error, use OpenSSH 4.7p1 or later.
(5) Precautions on remote monitoring with JP1/IM - Manager in a cluster environment
When you execute remote monitoring with JP1/IM-Manager in a cluster environment, you cannot monitor messages that occur during failover.
(6) Precautions on name resolution of the target host of remote monitoring
OS settings are used for name resolution of the target host of remote monitoring. jp1hosts and jp1hosts2 of JP1/Base are not used.
(7) Precautions on remote log file monitoring
Files for symbolic links and hard links cannot be monitored by remote log file monitoring.