The FglAM contains a cache file size config parameter within config file 'fglam.config.xml':
<config:upstream max-queue-size="-1" max-disk-space="1024" max-batch-size="500" allow-runtime-change="true"/>
<config:upstream-verified max-queue-size="-1" max-disk-space="512" max-batch-size="250" allow-runtime-change="true"/>
<config:downstream max-queue-size="-1" max-disk-space="1024" max-batch-size="500" allow-runtime-change="true"/>
The FglAM cache file path is the following:
$FglAM\state\default\cache
The agent does not know when the FMS goes down, so it will continue to collect data and place the data into the FglAM’s queue. The FglAM handles all collected agent data and places this into the cache. So if the cache is full, it will discard old data. When the FMS become available again, the stored data will be submitted to the FMS. Based on this, it is possible some gaps in the graphs will appear.