The health of the statsmonitor service is temporarily detected as "Red" in vCenter Server

Products

• VMware vCenter Server

Issue/Introduction

• An alert is triggered indicating that the health status of the statsmonitor service in vCenter Server has changed from "Green" to "Red," but it returns to "Green" immediately.

statsmonitor status changed from green to red
statsmonitor status changed from red to green

• The following log entries are recorded in vmon.log during the affected time period:

yyyy-mm-ddThh:mm:ss.###Z| host-###| W003: <statsmonitor> Service api-health command's stderr: Service health xml file is stale. Current time: ###, expiration time: ###. Treating service health state RED.
yyyy-mm-ddThh:mm:ss.###Z| host-###| I005: <statsmonitor> Restarting service.

Environment

VMware vCenter Server 7.0

Cause

The vmon service may judge the statsmonitor service status as "Red" (abnormal) due to a temporary delay in updating the health check file (statsmonitor_health.xml), which is periodically updated by the statsmonitor service.

Note: If no significant abnormalities are recorded in the logs, the specific cause for the delayed file update may be difficult to identify, as it is likely due to a transient processing delay.

Resolution

No additional action is required.

When a status abnormality (Red) is detected for the statsmonitor service, it is automatically restarted by the vmon service. 
In most cases, the service will automatically return to "Green" within several tens of seconds to approximately one minute after detection.

Additional Information

The statsmonitor service is responsible for collecting statistics such as CPU, memory, and disk usage of the vCenter Server Appliance (VCSA). 
Even if this service temporarily stops or restarts, it does not affect the operation of other vCenter services, managed ESXi hosts, or running virtual machines.

Japanese KB: vCenter Server で statsmonitor サービスの健全性が一時的に「Red」として検知される (426966)