Aria Automation Azure cloud account data collection takes longer than 10 minutes before run again

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Data collection for Azure cloud accounts exceeds the standard 10-minute interval, sometimes taking 20 minutes or longer.

The following symptoms may be seen in provisioning-service logs:

• Enumeration via ResourceEnumerationService runs sequentially across all endpoints.
• High latency (~100ms+) to specific endpoints, such as Azure VMware Solution (AVS) hosted NSX-T, causes individual tasks to take several minutes.
• Intermittent HTTP 503 errors during SaaS enumeration (e.g. Azure storage) result in 60-second timeouts, further delaying the overall cycle.

Use the below command to review live logs while connected to Aria Automation shell: 

vracli logs --service provisioning-service-app -f | grep -Ei "ResourceEnumerationTaskService.*resources/endpoints/[[:xdigit:]]{8}(-[[:xdigit:]]{4}){3}-[[:xdigit:]]{12}"

Environment

• Aria Automation 8.18.x
• SaaS cloud account's

Cause

The Aria Automation data collection process for cloud accounts is sequential. If one or more endpoints (especially high-latency remote endpoints like AVS) take a long time to respond, it bottlenecks the entire discovery queue, delaying all subsequent endpoints in the organization.

Resolution

To minimize data collection latency, follow these recommendations:

1. Investigate Network Latency: Work with the network team to resolve high latency to SaaS endpoints. Local enumerations typically complete in under 60 seconds; significant deviations indicate network or routing issues.
2. Address Intermittent 503 Errors: Review SaaS (Azure) environment logs to identify the source of intermittent 503 responses, which add significant cumulative delays to the sequential discovery process.