An administrator has successfully deployed and configured the Application Monitoring Telegraf Agent to 30 virtual machines through VMware Cloud Foundation (VCF) Operations. After 24 hours, the…

Question

Options

• AThere is a time synchronization issue between the Telegraf Agent and the Cloud Proxy.
• BThe Service Discovery Management Pack has not been configured.
• CApplication monitoring has been configured to use a single Cloud Proxy rather than a Collector
• DThere is a compatibility issue between the version of Virtual Machine Hardware and VMware

• A
  80% (33)
• B
  12% (5)
• C
  5% (2)
• D
  2% (1)

Explanation

Application Monitoring in VCF Operations uses Telegraf agents running inside virtual machines. These agents forward metrics to the Cloud Proxy, which then sends them to the Operations analytics cluster. One of the most common reasons an agent stops reporting data--especially exactly 24 hours after deployment--is clock drift or time mismatch between the VM (running the Telegraf agent) and the Cloud Proxy. VCF Operations enforces strict timestamp validation. If the timestamps from the agent are outside the acceptable drift window, the Cloud Proxy rejects incoming data as invalid. In this case, the Telegraf agents appear installed and functional, but no new metrics are received by the analytics This is a well-known issue documented in VMware Aria/VCF Operations agent-based monitoring, Agents send metrics with local system time. Cloud Proxy enforces time validation to prevent corrupt metric ingestion. A drift >5 minutes commonly results in zero data collection despite healthy connectivity.

No community discussion yet for this question.