The Data Gaps are expected due to network latency as the Agent Manager is not residing on the same subnet with the VM's. This has caused the data gaps as the physical distance has an effect on how long it takes for Foglight connection to perform the executions.
From Foglight documentation:
Unlike the previous generation of system agents, the Infrastructure agents can be set up to monitor hosts remotely. A single Foglight Agent Manager can host many Infrastructure agents, remotely monitoring different hosts. The Cartridge for Infrastructure agents are best deployed on a Foglight Agent Manager that is closely located to the monitored host, for example on the same subnet. This is especially important for WindowsAgents because the communication interfaces they depend on are not well-suited to a high-latency environment, performing many remote operations to gather data. UnixAgents are also affected. A high latency between the Agent Manager and the monitored host can result in collections being skipped, and observed as gaps in data.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center