Reason 1: Polling is not completed.
Solution: Click on the monitor. The 'Next Polled At' of the Monitor Information page provides information of the time when the next polling will start.
Reason 2: Thresholds are not configured for health or threshold conditions are not met.
Solution: Attributes like health of web application or disk partition or thread pool or jdbc connection pool will not have any thresholds associated to it by default and that is not an issue. Once you associate thresholds to the required attributes then root cause analysis will be done and health will be shown.To do this, follow the given steps:
1. Create threshold profile. Refer to the Creating Threshold Profile section in the User Guide.
2. Associate thresholds with respective monitor. Refer to the Associating Threshold and Actions with Monitor section in the User Guide.
Reason 3: Dependencies are not configured for monitor in a monitor group.
Solution: Configure dependencies for health and refer to the Configuring dependencies in the User Guide for more information.
Reason 4: The monitor-specific details are not set.
Solution: To do this, click on the monitor and provide its configurations.