■Monitoring items of simple Polling (network communication)
1.Ping monitoring, 2.http monitoring, 3.https monitoring, 4.port monitoring
5.SQL monitoring: hinemosManager connects to the database through the JDBC Driver, so the JDBC of the database must be prepared Driver.
■Monitoring nodes must install HinemosAgent monitoring items
1.custom monitoring, 2.log file monitoring, 3.HinemosAgent monitoring, 4.windows event monitoring
■SNMP/WBEM polling
1. process monitoring, 2. resource monitoring (cpu, memory, disk), 3. SNMP monitoring
needs to be configured to add this configuration: view systemview included .1.3.6.1
※/etc/snmp/snmpd.conf, if If the HinemosAgent is installed on the object node,
there is no need to manually configure the snmp service (except for modifying the community name of course).
By default, the public community name responds to the read operation, but for security, you can define the community name you want to define,
and control Access source
such as:
#com2sec notConfigUser default public
com2sec infogrid_security 192.168.152.0/24 abc
■Using monitoring items to rsyslog service
1. System log monitoring
※If HinemosAgent is not installed on the node, then rsyslog needs to be configured.
If HinemosAgent is installed,
*.info;mail.none;authpriv.none;cron.none @@ 192.168.120.120:514
■Using monitoring items to WinRM
1.windows service monitoring
Note: After completing the settings according to Hinemosの administrator ガイドのWindowsサービス, remember that when adding a node, you need to configure the winrm service, including the login user name and password! If you don't match, you can't be monitored normally!
■About SNMPTRAP monitoring
SNMPTRAP monitoring works in the opposite way to other monitoring items. It is realized by the target machine sending SNMPTRAP messages to HinemosManager.
Other monitoring methods are realized by HinemosManager sending requests to each target node regularly.
It should be noted that, for example, to configure the SNMPTRAP monitoring item of idrac, the SNMPTRAP sending address (HinemosManager) must be written in idrac, and the
alert is a valid state. Otherwise, even if there is a problem, the HinemosManager side will not detect it.
By default, HinemosManager has some MIBs that are registered by default. If the monitored device has a special OID, you need to import the MIB information through the Hinemos Utility tool.
■JMX monitoring