
OPERATIONAL DEFECT DATABASE
...

...
Following algorithm is used before this health alert is shown: The total number of file events is counted and the percentage of these that failed to be sent for dynamic analysis or failed to be stored due to any of following three reasons is calculated: (1) Malware cache didn't get initialized at startup (2) Memory limit on file capture was reached (3) Memory limit on the file queue was reached and the percentage is compared against the threshold for the health alert. The health alert occurs if the percentage of file events having certain classes of errors in dynamic analysis *or storage* exceeds the threshold during a particular interval. These errors include not being able to send the file for dynamic analysis because not enough memory was available.
File policy configured to send files to public/private cloud and/or storage files locally could trigger the alert under certain circumstances. This was created to provide additional logging capabilities when this happens for troubleshooting purposes.
Not Known
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.