Study guide

16.2 Application & Guest Monitoring

VMware vSphere Foundation 9.0 Administrator VCP-VVF, 2V0-16.25

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Preparation Strategy

1.1 Exam Format, Passing Standard & Blueprint Structure 1.2 Preparation Strategy & Hands-On Lab Setup

2 Chapter 2: Virtualization & ESXi Host Fundamentals

2.1 Hypervisor Architecture & ESXi Operating Model 2.2 ESXi Deployment, DCUI & Initial Host Configuration 2.3 Workload Consolidation & Private Cloud Economics

3 Chapter 3: vCenter Server & Cluster Management

3.1 vCenter Server Appliance (VCSA) Architecture & Deployment 3.2 vSphere High Availability (HA) & Admission Control 3.3 Distributed Resource Scheduler (DRS) & EVC Configuration

4 Chapter 4: Virtual Machine Operations & Resource Management

4.1 Virtual Machine Provisioning, Templates & Content Libraries 4.2 Resource Allocation: Shares, Reservations & Limits 4.3 vMotion, Storage vMotion & Snapshot Management 4.4 Content Libraries, Publication & Template Versions

5 Chapter 5: vSphere Storage Architecture & Traditional Datastores

5.1 Block Storage Architecture, Fibre Channel & VMFS Datastores 5.2 NFS Datastores, Software iSCSI & Multipathing (NMP) 5.3 Storage Policy-Based Management (SPBM) Framework

6 Chapter 6: VMware vSAN Architecture & Storage Policies

6.1 vSAN Core Architecture: OSA vs Express Storage Architecture (ESA) 6.2 Deploying & Configuring a vSAN Cluster 6.3 vSAN Storage Policies, Resilience (FTT) & Fault Domains 6.4 vSAN Space Efficiency & Capacity Accounting

7 Chapter 7: vSphere Networking & Traffic Management

7.1 Standard Switches (vSS) vs Distributed Switches (vDS) 7.2 Port Groups, VMkernel Adapters & Traffic Isolation 7.3 NIC Teaming, Load Balancing, VLANs & NIOC

8 Chapter 8: VVF Deployment & Supervisor Configuration

8.1 VMware vSphere Foundation 9.0 Stack & Deployment Prerequisites 8.2 End-to-End VVF Deployment Workflow 8.3 Enabling & Configuring the vSphere Supervisor

9 Chapter 9: Identity, Licensing & Security Management

9.1 vCenter Single Sign-On (SSO), Identity Federation & RBAC 9.2 VVF 9.0 Core-Based Licensing & License Management 9.3 VMware Certificate Authority (VMCA) & TLS Configuration 9.4 Workload & Infrastructure Encryption

10 Chapter 10: Lifecycle Management with vLCM

10.1 vSphere Lifecycle Manager (vLCM) Image Architecture 10.2 Base Images, Vendor Add-ons & Hardware Support Managers (HSM) 10.3 Host Compliance Checks, Staging & Cluster Remediation

11 Chapter 11: VCF Operations: Performance, Capacity & Alerts

11.1 VCF Operations Architecture, Node Types & Adapters 11.2 Dashboards, Custom Views, Metrics & Reports 11.3 Capacity Planning, Rightsizing & Alert Policies

12 Chapter 12: VCF Operations for Logs & Compliance

12.1 VCF Operations for Logs Architecture & Ingestion 12.2 Interactive Log Analytics, Query Syntax & Dashboards 12.3 Security Hardening Compliance & Storage/App Monitoring

13 Chapter 13: Workload Consumption & Automation

13.1 vSphere VM Service: Classes, Images & Declarative Deployment 13.2 VMware Kubernetes Service & Workload Clusters 13.3 VCF Operations Orchestrator Workflows & Automation 13.4 Supervisor Services & vSphere Pods

14 Chapter 14: Operations Evidence, Policies & Financial Reporting

14.1 Metrics, Properties & Logs 14.2 Custom Views & Scheduled Reports 14.3 Effective Policies, Groups & Overrides 14.4 Cost Drivers, Pricing & Showback

15 Chapter 15: Log Integrations & Shared Operational Views

15.1 VVF Integrations & Log Events in Operations 15.2 Logs Dashboards, Queries & Sharing

16 Chapter 16: Guest Services & Application Monitoring

16.1 Configure Service Discovery 16.2 Application & Guest Monitoring

16.2 Application & Guest Monitoring

Key Takeaways Explain This Topic AI

Infrastructure metrics, guest/application metrics, logs and discovery answer different questions.

A connected agent still needs supported application inputs, credentials and current collection.

Validate feature-specific collector network paths, certificate trust and effective policy.

A VMDK expansion and guest filesystem expansion are separate operations.

Last updated: October 2026

Observe the Layer That Owns the Symptom

A VM can have spare hypervisor CPU and memory while its database connections are exhausted or its web service is unavailable. Application monitoring adds guest/application measurements to the infrastructure view. It complements vCenter metrics, Logs and Service Discovery; it does not make any one of them unnecessary.

Start with the application symptom and service objective. Useful measurements can include operating-system filesystem use, process health, web requests or database-specific counters, depending on supported integrations. A hypervisor virtual-disk capacity metric does not reveal every guest filesystem's free space. A running process does not prove a successful client transaction.

Select a Supported Collection Method

Operations supports application-monitoring paths using Telegraf and applicable integration/plugin configuration. Verify the supported guest OS, application/version, agent and collector before installation. Select a small representative scope and the required application metrics. Installing an agent is not the same as configuring a database input with valid access and enabling collection.

For Kubernetes workloads, use the supported VKS/Supervisor monitoring integration and agent configuration for that service/release. Do not install an arbitrary guest-VM agent into every container and assume it becomes cluster monitoring. Separate cluster/node health from application/container measurements and check the integration's object relationships.

Need Evidence Separate prerequisite

Guest filesystem capacity Collected filesystem metric for the actual mount Supported guest collection and correct mount identity

  • Service/process health Current application/service state Supported plugin and target configuration
  • Database performance Relevant database counters Correct application credentials and permissions

User-visible availability Approved synthetic/client test or application evidence Network path, authentication and endpoint behavior

  • Infrastructure correlation VM/host/storage relationships and measurements Healthy vCenter integration
  • Prepare and Deploy

Confirm guest and collector reachability, time and certificate trust. Use the installation workflow supported by the installed Operations version and record whether deployment needs guest credentials, administrative rights or preinstalled prerequisites. Restrict the runtime monitoring account to its documented privileges rather than leaving a general administrator credential in every plugin.

Cloud Proxy communication is feature-specific. Broadcom KB 374807 documents ports 443, 4505 and 4506 in applicable Telegraf monitoring communication. Validate the required direction and endpoints against the current port matrix; do not assume the single HTTPS connection used by another collector feature covers application monitoring.

Install/enable the supported agent on a representative VM, configure the intended application input and verify its collection state. Check current timestamps and at least one independently known value inside the guest/application. If the agent is connected but application fields are missing, inspect input configuration, application compatibility and credentials before reinstalling it.

Correlate Without Confusing Units

Suppose users report slow web responses while guest CPU remains low. Compare request rate/error/response-time data, guest memory and filesystem metrics, VM scheduling contention, storage latency and relevant logs for the same absolute interval. A database dependency or network connection issue can dominate response time even when CPU utilization is low.

Conversely, a high guest CPU percentage can reflect useful load rather than a hypervisor fault. Check host contention and application throughput. Rightsizing a VM requires understanding both demand and the application's concurrency/resource behavior; adding vCPUs is not the default response to every performance alert.

Configure a Useful Alert

Choose the correct object and metric, define an appropriate threshold or dynamic condition, add a wait/cancel behavior and provide a diagnostic recommendation. Use a controlled lab threshold to validate evaluation. Then enable the definition under the effective policy and test the outbound notification separately.

For example, an alert about a guest data filesystem nearing capacity must refer to that filesystem, not the entire datastore or a VM's configured virtual-disk size. Before automating expansion, check datastore headroom, virtual-disk/guest support, partition layout and the allowed maximum. Expanding the VMDK alone does not necessarily extend the guest filesystem.

Troubleshoot and Maintain

If measurements stop, check agent/service state, collector reachability, trust, application credentials, effective policy and the last successful sample. A certificate replacement can invalidate agent-to-collector trust. A plugin can remain installed while the target account expires. Preserve the relevant error and scope the repair to the affected layer.

Track deployment changes and agent/plugin versions. After an application upgrade, verify that expected metrics still exist and retain the same semantics/units. Remove or revise stale monitoring for decommissioned services so dashboards do not imply coverage that no longer exists. Review resource overhead under realistic event/metric volume rather than promising zero monitoring cost.

A complete exercise demonstrates a supported monitored application, a verified known measurement, a controlled fault or threshold, alert evaluation and authorized notification. Record how the application maps to its VM and supporting datastore/host. This evidence supports practical incident response and distinguishes deep application monitoring from a simple discovered service name.

Review Takeaways

Infrastructure metrics, guest/application metrics, logs and discovery answer different questions.

A connected agent still needs supported application inputs, credentials and current collection.

Validate feature-specific collector network paths, certificate trust and effective policy.

A VMDK expansion and guest filesystem expansion are separate operations.