Aria Automation status changes randomly from OK to Warning and vice versa

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Aria Automation adapter flaps from OK to Warning

In the logs, signature matching this will be observed:
logs/adapters/CASAdapter/CASAdapter_########.log:
YYYY-MM-DDTHH:MM:SS ERROR [Collector worker thread 2] (14879814) com.vmware.adapter#.cas.impl.CASAPIService.login - Unable to get the authentication token from VMware Aria Automation
YYYY-MM-DDTHH:MM:SS ERROR [Collector worker thread 4] (14879814) com.vmware.adapter3.cas.CASAdapter.updateMeteringPolicyPropertyOnSpecificResource - Exception in updating policy assignments in vRops
com.vmware.ops.api.client.exceptions.ClientSideException: No such Metering Policy - ########-####-####-####-############.

Environment

Aria Operations 8.18.x

Cause

Automation Adapter Instance might have incorrect credentials or network latency issues

Resolution

1. Ensure that in addition to Automation Assembler and Org owner roles, the Service Broker Admin service role is also enabled on Automation side. And the cloud account, within the integration account in Aria Operations, Automation Load Balancer's FQDN is used under IP/FQDN field, then  Validate Connection and examine the results
2. To eliminate any performance related causes, apply the below KBs on both Kubernetes and NSX adapters that exist in the environment.
   • For NSX adapter: Aria Operations stops collecting data due to large number of distinct NSX BGP Neighbor Instanced Metric metric keys
   • For Kubernetes: Analytics down - Aria Operations & The number of Objects Configured in Aria Operations is abnormally high