Study guide

8.5 Alarms & vCenter Appliance Health Monitoring

VMware Certified Professional - Data Center Virtualization VCP-DCV

Track your progress as you read

Finished sections get a check mark.

1 Introduction: VCP-DCV Exam Overview

About the VCP-DCV Exam (2V0-21.23)

2 Chapter 1: vSphere Architecture & Core Platform Technologies

1.1 vSphere 8.x Architecture and Components Overview 1.2 vCenter Server Appliance (vCSA) Architecture & Deployment 1.3 vSphere Distributed Services Engine (DSE) & DPUs 1.4 vSphere Products, Solutions & Workload Platform 1.5 vCenter Topology: SSO Domains & Enhanced Linked Mode 1.6 vSphere with Tanzu: Supervisor, Namespaces, Zones & Lifecycle 1.7 vSphere in the SDDC: vCenter Converter, vSphere Replication & SRM

3 Chapter 2: Compute Resources & Cluster Management

2.1 vSphere High Availability (HA) Architecture 2.2 Distributed Resource Scheduler (DRS) & Resource Pools 2.3 vMotion & Enhanced vMotion Compatibility 2.4 Virtual Machine Advanced Compute Configuration 2.5 Fault Tolerance, Proactive HA & Advanced Cluster Options 2.6 vSphere Cluster Services (vCLS) & Retreat Mode 2.7 Migration Types: Cold Migration, Storage vMotion & Cross vCenter Export

4 Chapter 3: Storage Technologies & VMFS Datastores

3.1 Storage Access Protocols & Multipathing 3.2 VMFS Datastore Architecture & Management 3.3 Storage Policies (SPBM) & Virtual Volumes (vVols) 3.4 Storage DRS & Storage I/O Control 3.5 RDM, PMem, NVMe, NVMe-oF & iSER Use Cases

5 Chapter 4: VMware vSAN Architecture & Operations

4.1 vSAN Core Architecture & Disk Groups 4.2 vSAN Fault Domains & Stretched Clusters 4.3 vSAN Storage Policies & Data Protection 4.4 vSAN Maintenance, Health Checks & Monitoring

6 Chapter 5: Virtual Networking Architecture & Configuration

5.1 Standard Switches (vSS) vs Distributed Switches (vDS) 5.2 Port Group Policies & NIC Teaming 5.3 VLAN Configuration & Security Policies 5.4 Network I/O Control (NIOC) & TCP/IP Stacks

7 Chapter 6: Security, Identity & Access Control

6.1 vCenter Single Sign-On (SSO) & Identity Sources 6.2 Role-Based Access Control (RBAC) & Global Permissions 6.3 Virtual Machine Encryption & Key Management 6.4 ESXi Host Security & vSphere Trust Authority 6.5 vSphere Certificate Management 6.6 VM Firmware, Secure Boot, vTPM & Virtualization-Based Security

8 Chapter 7: Lifecycle Management & Host Configuration

7.1 vSphere Lifecycle Manager (vLCM) Cluster Images 7.2 Baseline-Based Lifecycle Management 7.3 Host Profiles & Cluster Quickstart 7.4 Content Libraries & Virtual Machine Deployment 7.5 ESXi Host Configuration: Time, Services, Product Locker & Boot Options 7.6 vCenter Lifecycle: Update Planner, VAMI Patching & Upgrades 7.7 Virtual Machine Snapshots & VM Creation Methods

9 Chapter 8: Monitoring, Performance Tuning & Troubleshooting

8.1 Performance Monitoring & Metrics 8.2 Command-Line Diagnostics & esxtop 8.3 Log Analysis & Diagnostic Data Collection 8.4 Troubleshooting Common Infrastructure Scenarios 8.5 Alarms & vCenter Appliance Health Monitoring

8.5 Alarms & vCenter Appliance Health Monitoring

Key Takeaways Explain This Topic AI

vCenter ships predefined alarm definitions, such as host connection state, host CPU and memory usage, datastore usage on disk, and certificate status, defined at the vCenter root so every object inherits them.

A custom alarm is created by choosing a target type, one or more rules whose trigger is a condition or an event, a Warning or Critical severity, and actions such as email, SNMP traps, or running a script.

Acknowledging a triggered alarm stops its actions from repeating while the alarm stays visible; Reset to Green clears it manually, which event-based alarms often need.

The vCenter Server Management Interface (port 5480) shows appliance health for CPU, memory, database, storage, and swap, plus disk usage per partition, such as /storage/seat and /storage/log.

Email alarm actions need vCenter's mail settings, and SNMP trap actions need SNMP receivers, both configured under vCenter > Configure > Settings > General.

Last updated: September 2026

  • 8.5 Alarms & vCenter Appliance Health Monitoring
  • Predefined Alarms (7.10)

vCenter includes a large set of predefined alarm definitions , mostly defined on the vCenter Server root object , so they apply to every matching object below it. Examples:

  • Predefined Alarm Watches
  • Host connection and power state Hosts that disconnect or become not responding
  • Host CPU usage / Host memory usage Sustained high utilization
  • Virtual machine CPU usage / Virtual machine memory usage Sustained high VM utilization
  • Datastore usage on disk Datastore capacity: Warning at 75% and Critical at 85% by default
  • Cannot connect to storage Loss of storage paths or connectivity
  • vSphere HA alarms Failover in progress, host status, or insufficient failover resources
  • Certificate status Certificates close to expiring (Section 6.5)
  • vSAN health alarms Skyline Health findings for vSAN clusters
  • Host hardware alarms Sensor-based health (fans, power supplies, temperature)
  • Working with Triggered Alarms

Triggered alarms appear on the object and in Monitor > Issues and Alarms > Triggered Alarms .

Acknowledge: records that someone is handling the alarm and stops its actions from repeating . The alarm stays in the triggered list until the condition clears.

Reset to Green: manually clears an alarm. You often need this for event-based alarms, which have no condition that clears on its own.

Disable or edit a predefined definition where it is defined ( Configure > Alarm Definitions on the vCenter object). It is usually better to create a custom alarm than to change defaults.

Creating a Custom Alarm (7.11)

Go to the object where the alarm should apply (for example a datacenter, cluster, or datastore folder), then open Configure > Alarm Definitions > Add . The wizard has these steps:

Name and Targets: name the alarm and pick the target type , such as virtual machines, hosts, clusters, datastores, or networks. The alarm applies to objects of that type at or below where it is defined.

Alarm Rule: define IF and THEN :

IF: a condition or state (for example Datastore Disk Usage is above 90% for 5 minutes ) or an event (for example Host connection lost , or an SSO event such as com.vmware.sso.PrincipalManagement ).

THEN: set the severity to Warning or Critical , and add actions :

Send email notifications: requires vCenter's mail settings (SMTP server and sender) under vCenter > Configure > Settings > General .

Send SNMP traps: requires SNMP receivers in the same settings.

Run script: runs a command or script on the vCenter appliance.

For VM or host targets, some rules also offer VM or host actions , such as power operations or entering maintenance mode.

Choose how often actions repeat while the alarm stays triggered.

Add more rules if needed. Each rule can have its own severity and actions.

Reset Rule: decide when the alarm returns to normal, for example when usage drops below the threshold, or on a clearing event.

Review and Enable.

Tips:

Define alarms as high in the inventory as makes sense, so new objects inherit them.

Use a duration ("for 5 minutes") on metric conditions to avoid alerts from brief spikes.

Creating alarms needs the Alarms privileges on the object.

Monitoring the vCenter Server Appliance (5.2)

vCenter is itself a workload to watch. The vCenter Server Management Interface (VAMI) at https://<vcenter-fqdn>:5480 shows:

VAMI Area What to Check

Summary > Health Status Overall health plus CPU , Memory , Database , Storage , and Swap health, shown green, yellow, orange, or red

Monitor > CPU & Memory Appliance utilization trends

Monitor > Disks Usage per partition, such as /storage/log (logs), /storage/seat (statistics, events, alarms, tasks), /storage/db , and /storage/core

  • Monitor > Network Throughput and errors
  • Monitor > Database vPostgres usage, including growth of SEAT data
  • Services Status of each vCenter service, with start, stop, and restart

Common findings:

/storage/seat filling up from high statistics levels or long retention. Lower the statistics level (Section 8.1), shorten retention, or grow the disk.

/storage/log filling up after verbose logging. Revert the log levels and clean up.

Low memory warnings ("Appliance is running low on memory") on appliances sized too small, such as Tiny in production. Resize the appliance to the correct deployment size.

From the appliance shell, service-control --status --all lists the state of every vCenter service. In the vSphere Client, Monitor > Skyline Health runs health checks for vCenter and vSAN.

Scenario: Designing Useful Alarm Coverage

A new cluster goes live, and the operations team wants to know about problems without drowning in email. A sensible plan:

Keep the predefined alarms , but check their thresholds. On large datastores, 75% and 85% may be too early, so a copy of the alarm with a different threshold on the right folder may be better than editing the default.

Add custom alarms for business-specific risks, such as a datastore folder for a critical application, or VMs with snapshots that could fill storage.

Route actions: send email for Critical alarms and SNMP traps to the monitoring platform. Set the repeat interval so the same alarm doesn't send new messages every few minutes.

Use event-based alarms for security-relevant changes, for example SSO principal management events, and reset them to green after review.

Watch vCenter itself: check the VAMI health, especially /storage/seat and /storage/log usage, and the vCenter service status after every patch.