Comparing CHM and SHM: Understanding their fundamental differences
This topic outlines the purpose and usage of Cluster Health Monitor (CHM) and System Health Monitor (SHM).
| Cluster Health Monitor (CHM) | System Health Monitor (SHM) |
|---|---|
Known as system monitor daemon ( osysmond ) is a real-time monitoring and operating system metric collection daemon that runs on each cluster node on RAC systems. | known as system Health Monitor ( ahf-sysmon ) is a real time monitoring and operating system collection service available on Single-Instance Database and non-GI based systems. |
| Integrated and enabled by default as part of GI since 11.2. | Integrated and enabled by default as part of AHF 24.6 |
Runs as system monitor service ( osysmond ) from GI home. | Runs as ahf-sysmon service from AHF home. |
| Managed as High Availability Services (HAS) resource within GI stack. | Managed as tfa-monitor resource within AHF stack. |
Status of the resource can be queried using below command: | Status of the process can be queried using below command: |
Generated operating system metrics gets stored in Metric Repository is auto-managed on the above local filesystem.
| Generated operating system metrics gets stored in Metric Repository is auto-managed on the above local filesystem.
|
Above generated operating system metrics are collected as part tfactl diagcollect . | Above generated operating system metrics are collected as part tfactl diagcollect . |
| Supported on Linux, Solaris, AIX, zLinux, ARM64, and Microsoft Windows platforms. | Supported only on Linux platform. |