If you want to ensure that a resource is running, you must configure resource monitoring for it.
If the resource monitor detects a failure, the following takes place:
Log file messages are generated, according to the configuration specified in the logging section of /etc/corosync/corosync.conf. By default, the logs are written to syslog, usually /var/log/messages.
The failure is reflected in the cluster management tools (Pacemaker GUI, HA Web Konsole crm_mon), and in the CIB status section.
The cluster initiates noticeable recovery actions which may include stopping the resource to repair the failed state and restarting the resource locally or on another node. The resource also may not be restarted at all, depending on the configuration and state of the cluster.
If you do not configure resource monitoring, resource failures after a successful start will not be communicated, and the cluster will always show the resource as healthy.
Learn how to add monitor operations to resources with the GUI in Adding or Modifying Monitor Operations. If you prefer the command line approach, see Section 6.3.8, Configuring Resource Monitoring.