Aria Operations 8.14.1.22798983 Cloud Proxy becomes unresponsive

Products

• VMware Aria Suite

Issue/Introduction

The goal of this knowledge base article is to provide guidelines for cloud proxy sizing when data collection is degraded due to higher demand on cloud proxy collection.

Environment

Aria Operations 8.12 

Aria Operations 8.16

Aria Operations 8.18

Cause

Aria Operations cloud proxy was configured as small, but data collection is exceeding metric collection, and the following error messages are displayed in the adapter collection logs:

2024-01-25T18:43:50,066+0000 WARN [Collector worker thread 14] (91262) com.vmware.adapter3.amazonaws.AWSCloudwatchManager.getCollectionResults - Skipping metric EBSReadBytes
java.util.concurrent.ExecutionException: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Acquire operation took longer than the configured maximum time. 

Resolution

 

The error indicates that a request cannot get a connection from the pool within the specified maximum time.

This issue can be caused to high request rate, or the specific adapter requires increased processing. 

To resole the issue, deploy a standard cloud proxy.  See additional information below.

Additional Information

A small cloud proxy can not be modified after it is deployed. Hence, if capacity needs to be increased, it will require deploying a new cloud proxy selecting standard sizing, instead of small.

A standard cloud will require :

• 4vCPU
• 32gb of memory

The above configuration should allow for data collection for up to 40K objects.

sizing guidelines for Aria Operations 8.1x
Cloud Proxy Sizing Guidelines