Resolving High VM Object Churn Alerts in VCF Operations for Networks 6.14.0
Article ID: 442534
Updated On:
Products
Issue/Introduction
In VCF Operations for Networks, high churn is observed for the VM object type, resulting in persistent alerts within the application interface. This issue is typically encountered following a restart of Flink services.
Environment
VMware VCF Operations for Networks 6.14.x
Cause
Restarting Flink jobs initiates high data churn, which requires time to stabilize within the application interface.
When the default configuration for object version tracking is overly restrictive, the system triggers alerts even when there is no actual processing or indexer lag.This alert can be ignored since there is no processing lag / indexer lag. We can apply some workaround to suppress the alert.
Resolution
If you believe you have encountered this issue, open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.
Feedback
