VMware Technical Support routinely requests diagnostic information when you submit a support request. This diagnostic information contains product-specific logs and configuration files from the host on which the product runs.
Automation Orchestrator Appliance logs are stored in the /data/vco/usr/lib/vco/app-server/logs/ directory. You export the logs of your Automation Orchestrator Appliance deployment by logging in to the appliance command line and running the vracli log-bundle command. The generated log bundle is saved on the root folder of your Automation Orchestrator Appliance.
https://docs.vmware.com/en/VMware-Aria-Automation/8.17/Installing-Configuring-Automation-Orchestrator/G

When there is a conflict between constraint tags at different levels, the project-level constraint tags take precedence over the template-level constraint tags. This ensures that governance and compliance requirements set at the project level are always enforced, overriding the constraints set at the template level.
Thus, when the template is provisioned, thelocation:londontag from the project will take precedence over thelocation:bostontag from the template.
References:
* Using Automation Assembler project tags and custom properties
* Using constraint tags in Automation Assembler

A cloud zone in VMware Aria Automation is used to segregate resources for provisioning within a cloud account. It acts as a logical partition within a cloud account that organizes compute resources, which are used for deploying workloads. Cloud zones allow administrators to control the distribution of resources and ensure that specific projects or business units can deploy their workloads only within the designated zones.
This segregation helps in managing resource allocation more efficiently and can also support various organizational policies and compliance requirements by isolating environments such as development, testing, and production.
References:
* Using cloud zones in VMware Aria Automation

For the VMware Aria Automation onboarding plan to run successfully, two critical pre-requisites must be met:
* Add the cloud account and create cloud zones for compute resources where machines to be onboarded are located:This ensures that the necessary cloud infrastructure is available and properly configured for onboarding. Cloud zones represent specific regions or sets of resources within the cloud provider that will host the onboarded machines.
* Create a project with at least one user and give the project access to the cloud zones:Projects in VMware Aria Automation define boundaries for resource usage, permissions, and policies. By assigning at least one user to the project and ensuring the project has access to the relevant cloud zones, the onboarding process can allocate and manage resources as needed within the defined scope.
These steps ensure that the infrastructure and permissions are correctly set up to support the onboarding of virtual machines, providing a smooth and controlled process for integrating existing resources into VMware Aria Automation.
References:
* VMware Aria Automation Documentation
* VMware Aria Suite Overview

When collecting logs related specifically to the embedded VMware Aria Automation Orchestrator, you will find them in the path:/pods/prelude/vco-app-service. This directory contains the logs for the Orchestrator service, which are crucial for troubleshooting and analyzing the orchestration activities within VMware Aria Automation.
References
* VMware Aria Automation Orchestrator Logs