Academy/VVS/Intelligent Logging & Analytics
This solution targets VCF 5.2

Intelligent Logging and Analytics for VMware Cloud Foundation

VCF 5.2architectvcdxadminautomationPages 237-337; design decisions appendix pp.321-337 (53 decisions)

Provides centralized logging for VCF management and VI workload domains using VMware Aria Operations for Logs (formerly vRealize Log Insight) 8.18.0. Deploys a 3-node medium-sized Aria Operations for Logs cluster per VCF instance with Integrated Load Balancer (ILB) behind a VIP; syslog and agent-based log collection for ESXi, vCenter, NSX Manager, NSX Edge, SDDC Manager, Workspace ONE Access, VMware Aria Suite Lifecycle; content pack management; retention and archiving; event forwarding for multi-VCF deployments; AD-based RBAC.

Key Components: NSX, Aria Operations, Aria Automation, SDDC Manager, vCenter, ESXi, Workspace ONE

External dependencies: VMware Aria Operations for Logs 8.18.0 (deployed per VCF instance)

Design Decisions
Implementation
Operations
VCDX Defense
Quiz (15)
Flashcards (15)

53 design decisions. The Quality column is the Academy's assessment for defence practice; the VVS documents do not classify decisions by design quality (D133).

DD-IDDecisionQuality (Academy view)
ILA-VAOL-CFG-001Deploy a three node VMware Aria Operations for Logs cluster - one primary and two worker nodes with…AvailabilityPerformanceManageability

Decision: Deploy a three node VMware Aria Operations for Logs cluster - one primary and two worker nodes with an integrated load balancer, in the default management vSphere cluster.

Rationale: • Provides high availability. • Using the integrated load balancer prevents a single point of failure. • Using the integrated load balancer simplifies the VMware Aria Operations for Logs deployment and subsequent integration.

Implication: • You must deploy a minimum of three medium-size nodes. • You must size all nodes identically. • If the capacity of your VMware Aria Operations for Logs cluster must expand, identical capacity must be added to each node.

Component: VAOL

ILA-VAOL-CFG-002To deploy VMware Aria Operations for Logs, use the VMware Aria Suite Lifecycle instance in the…Manageability

Decision: To deploy VMware Aria Operations for Logs, use the VMware Aria Suite Lifecycle instance in the corresponding VMware Cloud Foundation instance.

Rationale: VMware Aria Operations for Logs product binary is downloaded directly to VMware Aria Suite Lifecycle in VMware Cloud Foundation mode.

Implication: You must deploy VMware Aria Suite Lifecycle in each VMware Cloud Foundation instance.

Component: VAOL

ILA-VAOL-CFG-003Protect all VMware Aria Operations for Logs cluster nodes by using vSphere High Availability.AvailabilityManageability

Decision: Protect all VMware Aria Operations for Logs cluster nodes by using vSphere High Availability.

Rationale: Supports the availability objectives for VMware Aria Operations for Logs without requiring manual intervention during an ESXi host failure event.

Implication: None.

Component: VAOL

ILA-VAOL-CFG-004Apply a vSphere Distributed Resource Scheduler (DRS) anti-affinity rule to the VMware Aria…AvailabilityManageability

Decision: Apply a vSphere Distributed Resource Scheduler (DRS) anti-affinity rule to the VMware Aria Operations for Logs cluster virtual machines.

Rationale: Using vSphere DRS prevents the VMware Aria Operations for Logs cluster virtual machines from running on the same ESXi host and risking the high availability of the cluster.

Implication: • You must perform additional configuration to set up an antiaffinity rule. • For a default management vSphere cluster that consists of four ESXi hosts, only a single ESXi host can enter maintenance mode at the same time.

Component: VAOL

ILA-VAOL-CFG-005Place the VMware Aria Operations for Logs cluster virtual machines in a dedicated virtual machine…AvailabilityManageability

Decision: Place the VMware Aria Operations for Logs cluster virtual machines in a dedicated virtual machine folder.

Rationale: Provides an organization of the VMware Aria Operations for Logs nodes in the management domain inventory.

Implication: You must create the virtual machine folder.

Component: VAOL

ILA-VAOL-CFG-006When using two availability zones, add the VMware Aria Operations for Logs cluster virtual machines…AvailabilityManageability

Decision: When using two availability zones, add the VMware Aria Operations for Logs cluster virtual machines to the first availability zone VM group.

Rationale: Ensures that, by default, the VMware Aria Operations for Logs cluster virtual machines are powered on within the first availability zone hosts group.

Implication: If VMware Aria Operations for Logs is deployed after the creation of the stretched cluster for management domain availability zones, the VM group for the first availability zone virtual machines must be updated to include the VMware Aria Operations for Logs cluster nodes.

Component: VAOL

ILA-VAOL-CFG-007In an environment with multiple VMware Cloud Foundation instances, deploy a three node VMware Aria…AvailabilityPerformanceManageability

Decision: In an environment with multiple VMware Cloud Foundation instances, deploy a three node VMware Aria Operations for Logs cluster the default management vSphere cluster in each VMware Cloud Foundation instance.

Rationale: Provides a local VMware Aria Operations for Logs infrastructure to each VMware Cloud Foundation instance for both availability, scale and performance reasons.

Implication: You must deploy VMware Aria Suite Lifecycle in each VMware Cloud Foundation instance.

Component: VAOL

ILA-VAOL-CFG-008In an environment with multiple VMware Cloud Foundation instances, place the VMware Aria Operations…AvailabilityManageability

Decision: In an environment with multiple VMware Cloud Foundation instances, place the VMware Aria Operations for Logs cluster virtual machines in each instance in a dedicated virtual machine folder.

Rationale: Provides an organization of the VMware Aria Operations for Logs cluster nodes in the management domain inventory.

Implication: You must create the virtual machine folder.

Component: VAOL

ILA-VAOL-CFG-009Deploy each node in the VMware Aria Operations for Logs cluster as a medium-size appliance.AvailabilityPerformanceManageability

Decision: Deploy each node in the VMware Aria Operations for Logs cluster as a medium-size appliance.

Rationale: • Accommodates the expected approximately 200 syslog and VMware Aria Operations for Logs agent connections. • Using medium-size nodes ensures that the storage space for the VMware Aria Operations for Logs cluster is sufficient for seven days of data retention.

Implication: You must scale-up the appliance size of the VMware Aria Operations for Logs nodes if the number of log sources exceeds the connection threshold for a medium-sized appliance.

Component: VAOL

ILA-VAOL-CFG-010Configure a retention period for the medium-size VMware Aria Operations for Logs appliance…PerformanceManageability

Decision: Configure a retention period for the medium-size VMware Aria Operations for Logs appliance according to the design objectives.

Rationale: Accommodates logs from the expected number of logging sources in this SDDC design.

Implication: None.

Component: VAOL

ILA-VAOL-CFG-011Apply an archive policy for the medium-size VMware Aria Operations for Logs appliance according to…PerformanceManageability

Decision: Apply an archive policy for the medium-size VMware Aria Operations for Logs appliance according to the design objectives.

Rationale: Accommodates historical logs according to the design objectives.

Implication: You must provide enough shared storage space in each VMware Cloud Foundation instance for log archival according to the design objectives.

Component: VAOL

ILA-VAOL-CFG-012Provide an NFS version 3 shared storage to the VMware Aria Operations for Logs cluster in each…AvailabilityPerformanceManageability

Decision: Provide an NFS version 3 shared storage to the VMware Aria Operations for Logs cluster in each VMware Cloud Foundation instance according to the design objectives.

Rationale: Accommodates log archiving according to the design objectives.

Implication: • You must maintain the VMware Aria Operations for Logs archive data blobs stored on the NFS shared storage, selectively cleaning the datastore when more space is required. • If you configure more logging sources to send logs to VMware Aria Operations for Logs or if you add VMware Aria Operations for Logs worker nodes, you must increase the size of the NFS shared storage. • You must enforce the archive policy directly on the shared storage. • If the NFS mount does not have enough free space or is unavailable for a period greater than the retention period of the appliance, VMware Aria Operations for Logs stops ingesting new data until the NFS mount has enough free space, becomes available, or archiving is deactivated. • When using two availability zones, ensure that the NFS share is available in both availability zones.

Component: VAOL

ILA-VAOL-CFG-013Configure alert notifications.Manageability

Decision: Configure alert notifications.

Rationale: Activates alerts from VMware Aria Operations for Logs sent to administrators and operators.

Implication: If using email for notifications, you must configure the SMTP server settings in VMware Aria Operations for Logs.

Component: VAOL

ILA-VAOL-CFG-014Install the following content packs: • Linux - Systemd • VMware - NSX •…Manageability

Decision: Install the following content packs: • Linux - Systemd • VMware - NSX • VMware-Aria-SuiteLifecycle-8.12+ • VMware Workspace ONE Access

Rationale: Provides additional granular monitoring on the virtual infrastructure. The following content packs are installed by default in VMware Aria Operations for Logs: • VMware - vSphere • VMware - vSAN The following content packs are installed automatically by SDDC Manager. • Linux - Systemd • VMware - NSX • VMware - VMware-AriaSuite-Lifecycle-8.12+

Implication: You must manually install the VMware Workspace ONE Access content pack.

Component: VAOL

ILA-VAOL-CFG-015Configure the following agent groups that are related to content packs: • VMware Aria Suite…Manageability

Decision: Configure the following agent groups that are related to content packs: • VMware Aria Suite Lifecycle • Photon OS • Workspace ONE Access

Rationale: • Provides a standardized configuration that is pushed to all VMware Aria Operations for Logs agents in each of the groups. • Supports collection according to the context of the applications and parsing of the logs generated from the SDDC components by the VMware Aria Operations for Logs agent, such as specific log directories, log files, and logging formats. • SDDC Manager creates the vRSLCM agent group.

Implication: Adds minimal load to VMware Aria Operations for Logs.

Component: VAOL

ILA-VAOL-CFG-016Connect VMware Cloud Foundation VI workload domains to VMware Aria Operations for Logs by using…Manageability

Decision: Connect VMware Cloud Foundation VI workload domains to VMware Aria Operations for Logs by using SDDC Manager.

Rationale: SDDC Manager automatically adds the VI workload domain vCenter Server and ESXi hosts to VMware Aria Operations for Logs.

Implication: None.

Component: VAOL

ILA-VAOL-CFG-017Install and configure the VMware Aria Operations for Logs agent on the clustered Workspace ONE…AvailabilityManageability

Decision: Install and configure the VMware Aria Operations for Logs agent on the clustered Workspace ONE Access nodes to send logs to the VMware Aria Operations for Logs cluster in their corresponding VMware Cloud Foundation instance.

Rationale: Provides a standardized configuration that is pushed to the VMware Aria Operations for Logs agents for each Workspace ONE Access node. Supports collection according to the context of the Workspace ONE Access using the VMware Aria Operations for Logs Ingestion API and parses of the logs by the VMware Aria Operations for Logs agent, such as specific log directories, log files, and logging formats.

Implication: None.

Component: VAOL

ILA-VAOL-CFG-018Configure the SDDC - Workspace ONE Access and SDDC - Photon OS agent groups in the VMware Aria…AvailabilityManageability

Decision: Configure the SDDC - Workspace ONE Access and SDDC - Photon OS agent groups in the VMware Aria Operations for Logs cluster to include the clustered Workspace ONE Access nodes.

Rationale: Provides a standardized configuration that is pushed to the VMware Aria Operations for Logs agents for each Workspace ONE Access appliance. Supports collection according to the context of the Workspace ONE Access using the VMware Aria Operations for Logs ingestion API and parses of the logs by the VMware Aria Operations for Logs agent, such as specific log directories, log files, and logging formats.

Implication: Adds minimal load to the VMware Aria Operations for Logs cluster.

Component: VAOL

ILA-VAOL-CFG-019Configure logging sources and VMware Aria Operations for Logs agents to send log data to the FQDN…AvailabilityManageability

Decision: Configure logging sources and VMware Aria Operations for Logs agents to send log data to the FQDN of the VMware Aria Operations for Logs integrated load balancer (ILB).

Rationale: • Ensures proper communication configuration - VMware Aria Operations for Logs can resolve the FQDN to the ILB IP address. • Provides potential to scale-out without reconfiguring all log sources with a new destination address. • Simplifies the configuration of log sources in the SDDC.

Implication: • You must enable the integrated load balancer on the VMware Aria Operations for Logs cluster. • You must configure valid DNS forward (A) and reverse (PTR) records for the integrated load balancer VIP.

Component: VAOL

ILA-VAOL-CFG-020Configure all vCenter Server instances as syslog sources to send log data directly to VMware Aria…Manageability

Decision: Configure all vCenter Server instances as syslog sources to send log data directly to VMware Aria Operations for Logs in their corresponding VMware Cloud Foundation instance.

Rationale: Simplifies configuration for log sources that are syslogcapable. The configuration is performed by SDDC Manager

Implication: • Certain dashboards in VMware Aria Operations for Logs require the use of the VMware Aria Operations for Logs agent for proper ingestion. • Not all operating system level events are forwarded to VMware Aria Operations for Logs.

Component: VAOL

ILA-VAOL-CFG-021Configure the VMware Aria Operations for Logs agent on the SDDC Manager appliance in each VMware…Manageability

Decision: Configure the VMware Aria Operations for Logs agent on the SDDC Manager appliance in each VMware Cloud Foundation instance to forward logs to the local VMware Aria Operations for Logs instance.

Rationale: Ensures relevant logs are sent to VMware Aria Operations for Logs from SDDC Manager. The integration is performed automatically by SDDC Manager.

Implication: None.

Component: VAOL

ILA-VAOL-CFG-022Configure the VMware Aria Operations for Logs agent on the VMware Aria Suite Lifecycle appliance to…Manageability

Decision: Configure the VMware Aria Operations for Logs agent on the VMware Aria Suite Lifecycle appliance to forward logs to VMware Aria Operations for Logs in its corresponding VMware Cloud Foundation instance.

Rationale: Simplifies configuration of log sources in the SDDC that are pre-packaged with the VMware Aria Operations for Logs agent. The integration is performed automatically by SDDC Manager.

Implication: None.

Component: VAOL

ILA-VAOL-CFG-023Configure the NSX components as syslog sources for VMware Aria Operations for Logs in their…Manageability

Decision: Configure the NSX components as syslog sources for VMware Aria Operations for Logs in their corresponding VMware Cloud Foundation instance, including: • NSX Manager instances • NSX Edge instances

Rationale: Simplifies configuration of log sources in the SDDC that are syslog-capable. NSX Manager instances are configured by SDDC Manager.

Implication: You must configure NSX components to forward logs to the VMware Aria Operations for Logs VIP. Not all operating system-level events are forwarded to VMware Aria Operations for Logs. You must manually configure NSX Edge instances.

Component: VAOL

ILA-VAOL-CFG-024Configure the logging sources, such as ESXi, vCenter Server, and NSX to communicate with VMware…PerformanceManageability

Decision: Configure the logging sources, such as ESXi, vCenter Server, and NSX to communicate with VMware Aria Operations for Logs, using the TCP protocol.

Rationale: Using the TCP syslog protocol ensures reliability and supports retry mechanisms. TCP syslog traffic is secure and more consistent with RFC 5424.

Implication: • TCP has a higher performance overhead compared to UDP. • You must manually deactivate the SSL connection requirement in VMware Aria Operations for Logs.

Component: VAOL

ILA-VAOL-CFG-025Do not configure VMware Aria Operations for Logs to automatically update all deployed agents.Manageability

Decision: Do not configure VMware Aria Operations for Logs to automatically update all deployed agents.

Rationale: Individually update the versions of the VMware Aria Operations for Logs agents for each of the specified components in the SDDC for precise maintenance.

Implication: You must maintain manually the VMware Aria Operations for Logs agents on each of the SDDC components.

Component: VAOL

ILA-VAOL-CFG-026In an environment with multiple VMware Cloud Foundation instances, forward logs to the other…AvailabilityPerformanceManageability

Decision: In an environment with multiple VMware Cloud Foundation instances, forward logs to the other instance by using the Ingestion API.

Rationale: Supports the following operations: • Structured and unstructured data for client-side compression • Log throttling from one VMware Aria Operations for Logs cluster to another. In the event of a crossinstance outage, the administrator has access to all logs from the two VMware Cloud Foundation instances although one of the instances is offline.

Implication: • You must configure each VMware Aria Operations for Logs cluster to forward log data to the cluster in the other VMware Cloud Foundation instance. The configuration introduces administrative overhead to prevent recursion of logging between instances using inclusion and exclusion tagging. • Log forwarding adds load to each instance. You must consider log forwarding in the sizing calculations for the VMware Aria Operations for Logs cluster in each instance. • You must configure identical size on both source and destination clusters.

Component: VAOL

ILA-VAOL-CFG-027In an environment with multiple VMware Cloud Foundation instances, configure log forwarding to use…AvailabilitySecurityManageability

Decision: In an environment with multiple VMware Cloud Foundation instances, configure log forwarding to use SSL on port 9543.

Rationale: Ensures that the log forward operations between instances are secure.

Implication: You must set up a custom CA-signed SSL certificate. Event forwarding with SSL does not work with the self-signed certificate that is installed on the destination servers by default. • If you add VMware Aria Operations for Logs nodes to a cluster, the SSL certificate used by the VMware Aria Operations for Logs cluster in the other VMware Cloud Foundation instance must be installed in the Java keystore of all nodes before SSL can be used.

Component: VAOL

ILA-VAOL-NET-001Place the VMware Aria Operations for Logs cluster nodes on the local-instance NSX network segment.AvailabilityManageability

Decision: Place the VMware Aria Operations for Logs cluster nodes on the local-instance NSX network segment.

Rationale: Provides a consistent deployment model for management applications.

Implication: You must use an implementation in NSX to support this networking configuration.

Component: VAOL

ILA-VAOL-NET-002Allocate statically assigned IP addresses from the local-instance NSX segment to the VMware Aria…AvailabilityManageability

Decision: Allocate statically assigned IP addresses from the local-instance NSX segment to the VMware Aria Operations for Logs cluster nodes and the integrated load balancer (ILB).

Rationale: Ensures stability across the SDDC and makes it simpler to maintain and easier to track.

Implication: Requires precise IP address management.

Component: VAOL

ILA-VAOL-NET-003In an environment with multiple VMware Cloud Foundation instances, allocate statically assigned IP…AvailabilityManageability

Decision: In an environment with multiple VMware Cloud Foundation instances, allocate statically assigned IP addresses from each local-instance NSX segment to the VMware Aria Operations for Logs cluster nodes in the instance.

Rationale: Ensures stability across the SDDC and makes it simpler to maintain and easier to track.

Implication: Requires precise IP address management.

Component: VAOL

ILA-VAOL-NET-004Configure forward and reverse DNS records for all VMware Aria Operations for Logs cluster nodes and…AvailabilityManageability

Decision: Configure forward and reverse DNS records for all VMware Aria Operations for Logs cluster nodes and the integrated load balancer (ILB) VIP address.

Rationale: All nodes are accessible by using fully qualified domain names instead of by using IP addresses only.

Implication: You must provide DNS records for the VMware Aria Operations for Logs nodes.

Component: VAOL

ILA-VAOL-NET-005Enable the VMware Aria Operations for Logs integrated load balancer (ILB) for balancing incoming…AvailabilityManageability

Decision: Enable the VMware Aria Operations for Logs integrated load balancer (ILB) for balancing incoming traffic.

Rationale: Supports balancing ingestion traffic among the VMware Aria Operations for Logs nodes and high availability.

Implication: You must provide an extra IP address and FQDN for the integrated load balancer (ILB).

Component: VAOL

ILA-VAOL-NET-006Configure NTP on each VMware Aria Operations for Logs cluster node.AvailabilityManageability

Decision: Configure NTP on each VMware Aria Operations for Logs cluster node.

Rationale: VMware Aria Operations for Logs depends on time synchronization.

Implication: None.

Component: VAOL

ILA-VAOL-LCM-001Use VMware Aria Suite Lifecycle to perform the life cycle management of VMware Aria Operations for…Manageability

Decision: Use VMware Aria Suite Lifecycle to perform the life cycle management of VMware Aria Operations for Logs in each VMware Cloud Foundation instance.

Rationale: VMware Aria Suite Lifecycle manages the product binaries and VMware Aria Operations for Logs upgrades.

Implication: You must deploy VMware Aria Suite Lifecycle by using SDDC Manager. VMware Aria Suite Lifecycle manages patches, updates, and hot fixes for VMware Aria Operations for Logs.

Component: VAOL

ILA-VAOL-SEC-001Activate VMware Aria Operations for Logs integration with your identity source by using the Active…SecurityManageability

Decision: Activate VMware Aria Operations for Logs integration with your identity source by using the Active Directory over LDAP.

Rationale: Allows authentication to VMware Aria Operations for Logs using your identity source. Allows authorization through the assignment of roles to enterprise users and groups defined in your identity source.

Implication: None.

Component: VAOL

ILA-VAOL-SEC-002Create a security group in your directory services for VMware Aria Operations for Logs…AvailabilitySecurityManageability

Decision: Create a security group in your directory services for VMware Aria Operations for Logs administrators and assign the Super Admin role to the group.

Rationale: Streamlines the management of VMware Aria Operations for Logs roles for users. Provides the following access control features: • Access to VMware Aria Operations for Logs administration is granted to a managed set of individuals that are members of the security group. • You can introduce improved accountability and tracking organization owner access to VMware Aria Operations for Logs.

Implication: You must create the security group outside of the SDDC stack. You must maintain the life cycle and availability of the security group outside of the SDDC stack.

Component: VAOL

ILA-VAOL-SEC-003Create a security group in your directory services for VMware Aria Operations for Logs users and…AvailabilitySecurityManageability

Decision: Create a security group in your directory services for VMware Aria Operations for Logs users and assign the User role to the group.

Rationale: Streamlines the management of VMware Aria Operations for Logs roles for users. Provides the following access control features: • Access to the VMware Aria Operations for Logs user interface is granted to a managed set of individuals that are members of the security group. • You can introduce improved accountability and tracking organization owner access to VMware Aria Operations for Logs.

Implication: You must create the security group outside of the SDDC stack. You must maintain the life cycle and availability of the security group outside of the SDDC stack.

Component: VAOL

ILA-VAOL-SEC-004Create a security group in your directory services for VMware Aria Operations for Logs viewers and…AvailabilitySecurityManageability

Decision: Create a security group in your directory services for VMware Aria Operations for Logs viewers and assign the View Only Admin role to the group.

Rationale: Streamlines the management of VMware Aria Operations for Logs roles for users. Provides the following access control features: • Access to the VMware Aria Operations for Logs user interface is granted to a managed set of individuals that are members of the security group. • You can introduce improved accountability and tracking organization owner access to VMware Aria Operations for Logs.

Implication: • You must create the security group outside of the SDDC stack. • You must maintain the life cycle and availability of the security group outside of the SDDC stack.

Component: VAOL

ILA-VAOL-SEC-005Configure the password expiration policy for each VMware Aria Operations for Logs appliance.SecurityManageability

Decision: Configure the password expiration policy for each VMware Aria Operations for Logs appliance.

Rationale: • You configure the password expiration policy for the VMware Aria Operations for Logs appliance to align with the requirements of your organization which might be based on industry compliance standards. • The policy is applicable only to the local VMware Aria Operations for Logs appliance users.

Implication: You can manage the password expiration policy on the VMware Aria Operations for Logs appliance by using the virtual appliance console or ssh client.

Component: VAOL

ILA-VAOL-SEC-006Configure the password complexity policy for the VMware Aria Operations for Logs appliance.SecurityManageability

Decision: Configure the password complexity policy for the VMware Aria Operations for Logs appliance.

Rationale: • You configure the password complexity policy for VMware Aria Operations for Logs to align with the requirements of your organization which might be based on industry compliance standards. • The policy is applicable only to the local VMware Aria Operations for Logs users.

Implication: You can manage the password complexity policy on the VMware Aria Operations for Logs appliance by using the virtual appliance console or a Secure Shell (SSH) client.

Component: VAOL

ILA-VAOL-SEC-007Configure the account lockout policy for each VMware Aria Operations for Logs appliance.SecurityManageability

Decision: Configure the account lockout policy for each VMware Aria Operations for Logs appliance.

Rationale: • You configure the account lockout policy for VMware Aria Operations for Logs to align with the requirements of your organization which might be based on industry compliance standards. • The policy is applicable only to the local VMware Aria Operations for Logs appliance users.

Implication: You can manage the account lockout policy on the VMware Aria Operations for Logs appliance by using the virtual appliance console or a Secure Shell (SSH) client.

Component: VAOL

ILA-VAOL-SEC-008Change the VMware Aria Operations for Logs root password on a recurring or event-initiated schedule…SecurityManageability

Decision: Change the VMware Aria Operations for Logs root password on a recurring or event-initiated schedule by using the SDDC Manager user interface or API.

Rationale: • By default, the password for the VMware Aria Operations for Logs root account expires every 365 days. • When VMware Aria Operations for Logs is deployed into a VMware Cloud Foundation environment in VMware Aria Suite Lifecycle, the root password is managed from the SDDC Manager user interface or API, not VMware Aria Suite Lifecycle.

Implication: By using SDDC Manager, you manage the password change or automated password rotation schedule for the VMware Aria Operations for Logs root account in accordance with your organizational policies and regulatory standards.

Component: VAOL

ILA-VAOL-SEC-009Change the VMware Aria Operations for Logs admin account password on a recurring or event-initiated…SecurityManageability

Decision: Change the VMware Aria Operations for Logs admin account password on a recurring or event-initiated schedule by using the SDDC Manager UI or API.

Rationale: When VMware Aria Operations for Logs is deployed into a VMware Cloud Foundation environment in VMware Aria Suite Lifecycle, the admin password is managed from the SDDC Manager user interface or API, not VMware Aria Suite Lifecycle.

Implication: You must routinely perform the password change for the admin account by using the SDDC Manager UI or API.

Component: VAOL

ILA-VAOL-SEC-010Use a CA-signed certificate containing the VMware Aria Operations for Logs cluster node FQDNs, and…AvailabilitySecurityManageability

Decision: Use a CA-signed certificate containing the VMware Aria Operations for Logs cluster node FQDNs, and the ILB FQDN in the SAN attributes, when deploying VMware Aria Operations for Logs in each VMware Cloud Foundation instance.

Rationale: Configuring a CA-signed certificate ensures that the communication to the externally facing UI and API for VMware Aria Operations for Logs, and cross-product, is encrypted.

Implication: Using CA-signed certificates from a certificate authority might increase the deployment preparation time as certificate requests are generated and delivered.

Component: VAOL

ILA-VAOL-SEC-011Use a SHA-2 or higher algorithm when signing certificates.Security

Decision: Use a SHA-2 or higher algorithm when signing certificates.

Rationale: The SHA-1 algorithm is considered less secure and has been deprecated.

Implication: Not all certificate authorities support SHA-2.

Component: VAOL

ILA-VAOL-MON-001Forward alerts to VMware Cloud Foundation Operations.Manageability

Decision: Forward alerts to VMware Cloud Foundation Operations.

Rationale: Provides monitoring and alerting information that is pushed from VMware Aria Operations for Logs to VMware Cloud Foundation Operations for centralized administration.

Implication: None.

Component: VAOL

ILA-VAOL-MON-002Support launch in context with VMware Cloud Foundation Operations.AvailabilityManageability

Decision: Support launch in context with VMware Cloud Foundation Operations.

Rationale: Provides access to VMware Aria Operations for Logs for context-based monitoring of an object in VMware Cloud Foundation Operations.

Implication: You can register only one VMware Aria Operations for Logs cluster with VMware Cloud Foundation Operations for launch in context at a time.

Component: VAOL

ILA-VAOL-MON-003Configure the VMware Aria Operations for Logs integration in VMware Cloud Foundation Operations.AvailabilitySecurityManageability

Decision: Configure the VMware Aria Operations for Logs integration in VMware Cloud Foundation Operations.

Rationale: • Activates the Logs tab in VMware Cloud Foundation Operations. • Activates Troubleshoot with the Logs dashboard. • Activates VMware Aria Operations for Logs launch in context from VMware Cloud Foundation Operations.

Implication: You can register only one VMware Aria Operations for Logs cluster with VMware Cloud Foundation Operations at a time. You must manage the password life cycle of this endpoint.

Component: VAOL

ILA-VAOL-MON-004Configure the VMware Aria • Operations for Logs adapter to use the local-instance collector group.AvailabilityManageability

Decision: Configure the VMware Aria • Operations for Logs adapter to use the local-instance collector group.

Rationale: Local-instance components are configured to use the local collector group. • Offloads data collection for local management components from the analytics cluster.

Implication: None.

Component: VAOL

ILA-VAOL-MON-005Add a Ping adapter for the VMware Aria Operations for Logs cluster.AvailabilityManageability

Decision: Add a Ping adapter for the VMware Aria Operations for Logs cluster.

Rationale: Provides metrics on the availability of the VMware Aria Operations for Logs cluster.

Implication: You must add the adapter instances manually.

Component: VAOL

ILA-VAOL-MON-006Configure the Ping adapter to use the local-instance collector group.Availability

Decision: Configure the Ping adapter to use the local-instance collector group.

Rationale: • Local-instance components are configured to use the local collector group. • Offloads data collection for local management components from the analytics cluster.

Implication: None.

Component: VAOL

ILA-VAOL-MON-007In VMware Cloud Foundation Operations, add an application-to-application service account, for…AvailabilitySecurityManageability

Decision: In VMware Cloud Foundation Operations, add an application-to-application service account, for VMware Aria Operations for Logs Integration. Assign this user the default Administrator role.

Rationale: Establishes integration between VMware Aria Operations for Logs and VMware Cloud Foundation Operations.

Implication: You must maintain the life cycle and availability of the service account outside of the SDDC stack.

Component: VAOL

ILA-VAOL-MON-008Activate VMware Cloud Foundation Operations integration in VMware Aria Operations for Logs using…SecurityManageability

Decision: Activate VMware Cloud Foundation Operations integration in VMware Aria Operations for Logs using the VMware Cloud Foundation Operations service account.

Rationale: Integrating VMware Aria Operations for Logs alerts with VMware Cloud Foundation Operations allows you to view all information about your environment in a single user interface.

Implication: • You must maintain the life cycle of this integration. • When using Workspace ONE Access, you must specify the user account in the user@domain@source format for the integration. source is the name of the Workspace ONE Access authentication source created in VMware Cloud Foundation Operations, svc-vrli-vrops@rainpole.io@WorkspaceONE.

Component: VAOL

Prerequisites

  • VCF version in Support Matrix (5.1.0-5.2.1)
  • Environment configured per Before You Apply This Guidance
  • Intelligent Logging and Analytics tab in VCF Planning and Preparation Workbook
  • VCF instance healthy and fully operational
  • DNS forward/reverse records for 3 nodes + ILB VIP
  • Active Directory with DCs, service accounts, security groups
  • Microsoft Certificate Authority available
  • Aria Suite Lifecycle deployed via SDDC Manager
  • 400 GB NFS version 3 shared storage for archival (if using 90-day archive; ILA-VAOL-CFG-012)
  • IAM validated solution implemented (AD over LDAP in vCenter)
  • Optional: Workspace ONE Access (for vIDM auth) — this guidance uses AD over LDAP natively

Implementation Procedure

PowerShell implementation

  1. Install PowerShell modules (PowerCLI 13.2.1+, vSphere.SsoAdmin 1.3.9+, ImportExcel 7.8.5+, PowerVCF 2.4.0+, PowerValidatedSolutions 2.11.0+)
  2. Run Start-ValidatedSolutionMenu.
  3. Main menu 06. (ILA) Intelligent Logging and Analytics:
  • Menu 01: Generate JSON Specification File
  • Menu 02: Verify Prerequisites
  • Menu 03: Generate Signed Certificate from Microsoft Certificate Authority
  • Menu 05: End-to-End Deployment (deploys the Aria Ops for Logs cluster with its ILB and configures content packs, agent groups, identity sources, role assignments, archival and alert SMTP)
  • Menu 07: Configuration (solution interoperability, for example the Ping adapter in Aria Operations and, if multi-VCF, event forwarding) (VVS 1.0 p.276)

UI implementation steps

  1. Deploy Aria Suite Lifecycle from SDDC Manager (pre-req per LCM design)
  2. In Aria Suite Lifecycle, download Aria Ops for Logs 8.18 product bundle
  3. Create environment in Aria Suite Lifecycle; import OVA
  4. Deploy 3-node cluster with ILB: specify primary/workers/ILB FQDNs and static IPs
  5. Configure DNS records (A/PTR) for 3 nodes + ILB VIP
  6. Configure NTP, DNS, time zone
  7. Install CA-signed certificate via Suite Lifecycle locker
  8. Configure AD over LDAP identity source (ILA-VAOL-SEC-001)
  9. Assign AD groups to roles: Super Admin, User, View Only Admin (SEC-002/003/004)
  10. Install content packs: VMware - NSX, VMware-Aria-Suite-Lifecycle-8.12+, Linux-Systemd, Workspace ONE Access (manual)
  11. Configure agent groups: VMware Aria Suite Lifecycle, Photon OS, Workspace ONE Access
  12. Add VI workload domains to Aria Ops for Logs via SDDC Manager (CFG-016)
  13. Install and configure Aria Ops for Logs agent on clustered W1A nodes (CFG-017)
  14. Configure log retention + archiving: 7 days retention, 90 days archive on a 400 GB NFS version 3 share (CFG-012)
  15. Configure SMTP in Aria Ops for Logs for alert notifications (CFG-013)
  16. Configure ping adapter for cluster health (ILA-VAOL-MON-005/006)
  17. Multi-VCF: configure log forwarding between clusters via Ingestion API over SSL port 9543 (CFG-026/027)
  18. Verify operational state (see Operations section)

External services / integration points

  • Active Directory (AD)

Personas

PersonaResponsibilityComponent role or group
Cloud AdminFull Admin and User capabilities, including editing shared contentAria Operations for Logs: Super Admin
AdministratorFull Admin and User capabilities, including editing shared contentSuper Admin
UserInteractive Analytics, including editing shared contentUser
ViewerRead-only accessView Only Admin

Source: VVS 1.0 Table 217, Example Personas for Intelligent Logging and Analytics (p.298)

Day-2 Operations Tasks

Operational verification

After installation, upgrade or outage

Log in at the ILB FQDN with a local and then an AD account (ILA-VAOL-SEC-001/003); Management > Cluster shows each node Connected and the integrated load balancer Available (VVS 1.0 p.299); Integration > vSphere shows Collecting for each vCenter (ILA-VAOL-CFG-020, p.301); Management > Agents with the Photon OS - Appliance Agent Group lists each management appliance Active (p.302).

Verify log sources

After adding or upgrading components

ESXi hosts, vCenter, NSX Managers and Edges, SDDC Manager and the Aria/VCF components forward to the ILB (ILA-VAOL-CFG-020..024); VI workload domains are connected through SDDC Manager (ILA-VAOL-CFG-016); NSX Edges need manual syslog configuration.

Retention and archive

Monthly capacity review

Keep the retention period per design objectives (ILA-VAOL-CFG-010); confirm the NFS v3 archive share has space and the archive policy runs (ILA-VAOL-CFG-011/012); archived blobs are maintained by the operator.

Scale up or out

When log-source count or ingest grows

Scale appliance size per ILA-VAOL-CFG-009 or add worker nodes through Aria Suite Lifecycle; size nodes identically (ILA-VAOL-CFG-001).

Agent management

Per component update

Agents are not auto-updated (ILA-VAOL-CFG-025); update them with each component; keep agent groups and content packs current (ILA-VAOL-CFG-014).

Certificate management

Before expiry or on compromise

Replace the CA-signed certificate containing node and ILB FQDNs through Aria Suite Lifecycle (ILA-VAOL-SEC-010); in multi-instance estates event forwarding over SSL/9543 requires a CA-signed certificate (ILA-VAOL-CFG-027); re-trust on forwarding peers and agents.

Password management

Per policy

Set expiration/complexity/lockout on each appliance (ILA-VAOL-SEC-005..007); rotate the root password through the SDDC Manager UI or API (ILA-VAOL-SEC-008), not Aria Suite Lifecycle; rotate the admin user in the product UI.

Life cycle

Per release

Patch and upgrade through Aria Suite Lifecycle (ILA-VAOL-LCM-001); snapshot first; re-verify agents and integrations afterwards.

Alert forwarding

Continuous

Forward alerts to VCF Operations (ILA-VAOL-MON-001) and check the Operations for Logs management pack dashboards.

Monitoring Points

  • Verify 3-node cluster status in Aria Ops for Logs UI (Admin > Cluster)
  • Verify ILB VIP resolves via DNS; UI accessible via VIP FQDN
  • Verify AD authentication: log in with AD user from Super Admin/User/View Only Admin groups
  • Verify ingestion from each source (ESXi/vCenter/NSX/Edge syslog; SDDC Manager/W1A/Aria Suite Lifecycle agent)
  • Verify content packs installed and dashboards populate
  • Verify retention: oldest logs trimmed at 7 days; archive building up on NFS
  • Verify SMTP alert delivery (trigger test alert)
  • Verify ping adapter health dashboard populates
  • Multi-VCF: verify logs from remote instance appear in local cluster via Explore Logs filter
  • Verify with browser: no cert warning on VIP FQDN

Troubleshooting

Cluster shows a worker node Disconnected
Cause: Node restarted by vSphere HA (ILA-VAOL-CFG-003) or storage latency
Fix: Wait for the node to rejoin; check vSAN health; nodes must stay identically sized.
vSphere dashboards empty for a domain
Cause: vCenter not configured as a syslog source or integration credentials expired (ILA-VAOL-CFG-020)
Fix: Re-add the vCenter integration with the service account and confirm ESXi hosts forward syslog.
Archive policy fails
Cause: NFS v3 export unreachable or full (ILA-VAOL-CFG-012)
Fix: Restore the export, extend space, re-run the archive job.
Event forwarding between instances fails over SSL
Cause: Self-signed certificate in use (ILA-VAOL-CFG-027)
Fix: Install the CA-signed certificate on both clusters; forwarding with SSL does not work with self-signed certificates.
Root password rotation rejected in Aria Suite Lifecycle
Cause: Root is managed by SDDC Manager in VCF mode (ILA-VAOL-SEC-008)
Fix: Rotate from SDDC Manager password management.

Likely Panelist Questions

Q: Why three medium nodes with the integrated load balancer?

ILA-VAOL-CFG-001/009: availability through the ILB and node redundancy, sized for the design objectives; all nodes identical; scale up or add workers as sources grow.

Q: How is retention met without unbounded vSAN usage?

ILA-VAOL-CFG-010..012: retention per objectives on the appliances, archive policy to NFS v3 for historical logs; the operator maintains the archive blobs.

Q: Why one cluster per VCF instance?

ILA-VAOL-CFG-002/008/027: local collection inside each instance with Aria Suite Lifecycle per instance; cross-instance visibility through SSL event forwarding on 9543.

Failure Scenarios

Standalone appliance instead of a cluster
Impact: Single point of failure for all SDDC logging.
Mitigation: ILA-VAOL-CFG-001 three-node cluster with ILB and vSphere HA.
Single central cluster for several VCF instances
Impact: WAN dependency and lost local collection during a site issue.
Mitigation: One cluster per instance with event forwarding (ILA-VAOL-CFG-008/027).
No NFS archive
Impact: Retention silently truncated when the appliance disk fills.
Mitigation: ILA-VAOL-CFG-011/012 archive to NFS v3 and capacity monitoring.
Self-signed certificate on forwarding
Impact: SSL event forwarding fails between instances.
Mitigation: CA-signed certificate (ILA-VAOL-SEC-010, CFG-027).
Host failure
Impact: vSphere HA restarts the node; brief ingest reduction.
Mitigation: ILA-VAOL-CFG-003 plus anti-affinity so one host holds one node.

Trade-off Analysis

Medium nodes with archive vs larger nodes with longer local retention

Chosen: Medium nodes plus NFS archive (ILA-VAOL-CFG-009..012)

Justification: Lower vSAN consumption; archived logs are slower to query.

Root password via Aria Suite Lifecycle vs SDDC Manager

Chosen: SDDC Manager (ILA-VAOL-SEC-008)

Justification: Single rotation plane for VCF-managed appliances; the admin UI user remains a separate task.

Quiz — Intelligent Logging & Analytics

0/15
Q1
How many nodes does the default Aria Ops for Logs cluster deployment contain?
  • 5
  • 3 (1 primary + 2 workers)
  • 2
  • 1
ILA-VAOL-CFG-001: 3-node cluster with 1 primary + 2 workers behind ILB.
Q2
Which component performs lifecycle management of Aria Ops for Logs in this solution?
  • kubectl
  • SDDC Manager
  • VMware Aria Suite Lifecycle
  • Aria Ops for Logs self-LCM
ILA-VAOL-LCM-001: Aria Suite Lifecycle manages binaries and upgrades.
Q3
Default retention period for a medium-size appliance?
  • 30 days
  • 365 days
  • 7 days
  • 90 days
7 days retention for medium appliance; 90 days archive on 400 GB NFS version 3 shared storage.
Q4
How is the ILB (Integrated Load Balancer) accessed by clients?
  • Via VIP FQDN + dedicated IP
  • Via NSX Tier-1 Gateway
  • Via vCenter VIP
  • Directly on primary node
ILA-VAOL-NET-005: ILB requires extra IP + FQDN; all ingestion/UI traffic routes via ILB VIP.
Q5
Which protocol/port is used for multi-VCF event forwarding in this design?
  • Syslog UDP/514
  • RELP TCP/20514
  • Syslog TCP/1514
  • Ingestion API over SSL port 9543
ILA-VAOL-CFG-026/027: Ingestion API over SSL port 9543 with custom CA-signed cert (not default self-signed).
Q6
Which content pack requires MANUAL installation (not auto-installed by default or by SDDC Manager)?
  • VMware Workspace ONE Access
  • Linux - Systemd
  • VMware - NSX
  • VMware - vSphere
ILA-VAOL-CFG-014: Workspace ONE Access content pack requires manual installation.
Q7
How is the root password of the Aria Ops for Logs appliance managed when deployed via VCF?
  • Active Directory
  • vCenter SSO
  • SDDC Manager UI/API
  • Aria Suite Lifecycle
ILA-VAOL-SEC-008: root password managed from SDDC Manager UI/API, NOT Aria Suite Lifecycle.
Q8
Which role gives a user full visibility into admin info but user-only actions?
  • Dashboard User
  • Super Admin
  • User
  • View Only Admin
View Only Admin = view admin info + full User access; user cannot modify admin settings.
Q9
In multi-AZ mgmt domain, which group is the Aria Ops for Logs cluster bound to?
  • Second AZ
  • First AZ host group
  • Witness host
  • All AZs equally
ILA-VAOL-CFG-006: cluster runs in first AZ; fails over to second AZ on AZ failure.
Q10
What happens when the NFS archive share is unavailable beyond the retention period?
  • Aria Ops for Logs stops ingesting new data until space/availability restored
  • Cluster reboots
  • Logs auto-migrate to vSAN
  • Logs continue normally
ILA-VAOL-CFG-010-012 implications: ingestion stops until NFS available with free space, or archiving is deactivated.
Q11
Which ingestion type is used for ESXi host logs?
  • Agent
  • Ingestion API
  • Syslog
  • SNMP trap
ESXi logs via syslog; vCenter/NSX/NSX Edge also via syslog. SDDC Manager/W1A/Aria Suite Lifecycle via agent.
Q12
Authentication transition from Workspace ONE Access to AD over LDAP — first step?
  • Remove AD group assignments
  • Remove W1A integration
  • Reboot cluster
  • Delete AD service account
Step 1: remove AD group assignments (added via W1A auth) before configuring AD over LDAP.
Q13
What is the minimum shared NFS storage recommended for a 90-day archive on a medium appliance?
  • 100 GB
  • 400 GB
  • 1 TB
  • 200 GB
Solution recommends 400 GB NFS version 3 shared storage for log archival (ILA-VAOL-CFG-012).
Q14
PowerValidatedSolutions menu option for ILA?
  • 06
  • 12
  • 05
  • 04
Start-ValidatedSolutionMenu main menu: 06. (ILA) Intelligent Logging and Analytics (VVS 1.0 p.276). Option 12 is Cloud-Based Ransomware Recovery; 07 is Intelligent Operations Management.
Q15
Which alert type is deactivated by default in Aria Ops for Logs?
  • System alerts
  • All alerts
  • Content pack alerts
  • User-defined alerts
Content pack alerts deactivated by default; System alerts active for own health; User-defined active when created.

Flashcards — Intelligent Logging & Analytics

Card 1 of 15
Aria Ops for Logs cluster design
3-node: 1 primary + 2 workers behind Integrated Load Balancer (ILB); medium-sized appliances; deployed on management vSphere cluster.

Labs

Lab 1: Deploy 3-Node Aria Ops for Logs Cluster via Aria Suite Lifecycle

Deploy the 3-node medium-sized Aria Ops for Logs cluster with ILB in the management domain via Aria Suite Lifecycle.

Starting State: VCF 5.2 with Aria Suite Lifecycle deployed via SDDC Manager; DNS records for 3 nodes + ILB VIP; static IPs on local-instance NSX segment; NTP configured; CA-signed certificate available in Suite Lifecycle Locker.

  1. Log in to Aria Suite Lifecycle at https://<suitelifecycle_fqdn> as vcfadmin@local
  2. Lifecycle Operations > Environments > Create Environment (or add product to existing)
  3. Download Aria Ops for Logs 8.18 product bundle to Suite Lifecycle
  4. Create new Aria Ops for Logs deployment: cluster type = cluster with ILB; specify 3 nodes (primary + 2 workers)
  5. Configure network: management VLAN (local-instance NSX segment), static IPs, FQDNs, gateway, subnet mask, DNS servers, NTP servers
  6. Configure ILB: VIP IP + FQDN
  7. Select CA-signed certificate from Locker
  8. Apply vSphere HA + DRS anti-affinity rules (ILA-VAOL-CFG-003/004) post-deploy
  9. Run precheck; Submit
  10. Monitor deployment in Requests; wait for Complete
  11. Place VMs in designated folder (ILA-VAOL-CFG-005)
  12. For multi-AZ: add VMs to first AZ VM group (ILA-VAOL-CFG-006)
  13. Verify UI accessible at https://<ilb_vip_fqdn>

Lab 2: Configure Content Packs, Agent Groups, and AD RBAC

Install content packs, configure agent groups for VCF components, and assign AD groups to Aria Ops for Logs roles.

Starting State: Cluster from Lab 1 online; AD security groups gg-vrli-admins, gg-vrli-users, gg-vrli-viewers created; vCenter has AD over LDAP IdP configured (from IAM solution); Workspace ONE Access deployed and AD-integrated.

  1. In Aria Ops for Logs UI, Content packs > Content pack marketplace > Marketplace (VVS 1.0 p.292)
  2. Install: VMware - NSX, VMware-Aria-Suite-Lifecycle-8.12+, Linux - Systemd (auto-installed if SDDC Manager not done), VMware Workspace ONE Access (manual)
  3. Management > Agents > select the agent template from the All agents drop-down > Copy template, set the hostname filter and Save new group (VVS 1.0 p.294)
  4. Create 'VMware Aria Suite Lifecycle' group with parser config for Suite Lifecycle logs
  5. Create 'Photon OS' group with systemd/photon log parser
  6. Create 'Workspace ONE Access' group with W1A log parser
  7. Install Aria Ops for Logs agent on each clustered W1A node (CFG-017); add to Workspace ONE Access agent group
  8. Configuration > Authentication > Active Directory tile > ellipsis > Edit (VVS 1.0 p.291)
  9. Configure AD over LDAP: Domain=sfo.rainpole.io, Server=dc01.sfo.rainpole.io:636, Bind DN + password, CA cert
  10. Management > Access control > Users and groups tab > Directory groups > New group: gg-vrli-admins with Super Admin role (VVS 1.0 p.291)
  11. Repeat for gg-vrli-users (User), gg-vrli-viewers (View Only Admin)
  12. Sign out; log in as AD user from each group; verify role-scoped menu access
  13. Configuration > SMTP — configure for alert notifications (ILA-VAOL-CFG-013; VVS 1.0 p.289)

Lab 3: Configure Multi-VCF Event Forwarding with SSL on Port 9543

In a two-VCF-instance Holodeck deployment, configure event forwarding between Aria Ops for Logs clusters with CA-signed SSL.

Starting State: Two VCF instances (sfo and lax); 3-node Aria Ops for Logs cluster per instance; CA-signed SSL certs installed on each cluster; identical medium sizing; inclusion/exclusion tags defined (for VCF instance differentiation).

  1. On sfo cluster, export SSL certificate chain
  2. On lax cluster nodes: import sfo cluster cert into Java keystore (cd /usr/lib/loginsight/application/lib/jre/lib/security; keytool -import -alias sfo-vrli -file sfo.pem -keystore cacerts -storepass <pw>)
  3. Repeat reverse: import lax cluster cert into sfo nodes' Java keystore
  4. In the sfo Operations for Logs UI, open the log forwarding settings and add a destination (VVS 1.0 gives the design, ILA-VAOL-CFG-027, not the menu path; record the path your build shows)
  5. Protocol = Ingestion API; Host = lax ILB VIP FQDN; Port = 9543; SSL = Enabled; Tags (inclusion: inst=sfo)
  6. Save; verify destination status = Connected
  7. Repeat on lax cluster: destination = sfo ILB; Tags (inst=lax)
  8. In lax UI: Explore Logs > Filter tag inst=sfo; verify sfo logs visible
  9. In sfo UI: Explore Logs > Filter tag inst=lax; verify lax logs visible
  10. Test failure scenario: power down sfo cluster; verify lax still has access to all sfo logs via its local copy from forwarding
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.