Release

Date

Build Number

VMware Aria Operations for Logs 8.14.1

23 NOV 2023

22806512

Note: If you have already upgraded from VMware Aria Operations for Logs 8.12 to version 8.14 or 8.14 with the Hotfix, we recommend that do not upgrade to version 8.14.1. The version 8.14 with the Hotfix resolves the same upgrade related issues that version 8.14.1 resolves.

Check for additions and updates to these release notes.

About VMware Aria Operations for Logs

VMware Aria Operations for Logs delivers the best real-time and archived log management, especially for VMware environments. Machine learning-based intelligent grouping and high performance search enables faster troubleshooting across physical, virtual, and cloud environments. VMware Aria Operations for Logs can analyze terabytes of logs, discover structure in unstructured data, and deliver enterprise-wide visibility using a modern web interface.

For more information, see the VMware Aria Operations for Logs product documentation.

What's New

Here are some of the resolved issues in the 8.14.1 release of VMware Aria Operations for Logs:

Upgrade to VMware Aria Operations for Logs 8.14

While upgrading to VMware Aria Operations for Logs 8.14, the worker nodes are not upgraded after the primary node upgrade is complete. The manual workaround described in KB-95323 is automated in the 8.14.1 release to make sure the worker nodes are upgraded successfully.

Network-related issues while upgrading from 8.12 to 8.14

While upgrading VMware Aria Operations for Logs from version 8.12 to 8.14, the primary node doesn’t receive the complete network configuration. Therefore, it becomes inconsistent and blocks the rolling upgrade of the cluster. This problem primarily impacts clusters where the network is configured manually. The manual upgrade fails with similar symptoms as described in KB - 83225.

Certificate fixes while adding a new node

The newly joined node fails to apply the custom certificate uploaded to the cluster.

Active Directory user is locked after a single incorrect login attempt

When VMware Aria Operations for Logs is integrated with Active Directory and there are multiple domain controllers, a single incorrect login attempt might lock the user in Active Directory.

Compatibility

VMware Aria Operations for Logs 8.14.1 can be integrated with the following VMware products and versions:

  • VMware vCenter Server 7.0 or later (FIPS mode supported).

  • VMware Aria Operations 8.6 or later.

You can install and upgrade VMware Aria Operations for Logs using VMware Aria Suite Lifecycle. For more information, see the VMware Aria Suite Lifecycle Installation, Upgrade, and Management Guide.

Browser Support

VMware Aria Operations for Logs 8.14.1 supports the following browser versions. More recent browser versions also work with VMware Aria Operations for Logs, but have not been validated.

  • Mozilla Firefox 80.0 and above

  • Google Chrome 91.0 and above

  • Safari 13.1.2 and above

  • Microsoft Edge 91.0 and above

The minimum supported browser resolution is 1280 by 800 pixels.

Important: Cookies must be enabled in your browser.

VMware Aria Operations for Logs Agent Support

VMware Aria Operations for Logs Windows Agent Support

The VMware Aria Operations for Logs 8.14.1 Windows agent supports the following versions:

  • Windows 10, Windows 11 (supported, but not tested)

  • Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019.

VMware Aria Operations for Logs Linux Agent Support

The VMware Aria Operations for Logs 8.14 Linux agent supports the following distributions and versions:

  • RHEL 7, RHEL 8, and RHEL 9

  • SLES 12 SP5 (supported, but not tested), and SLES 15 SP3 (supported, but not tested)

  • Ubuntu 18.04, Ubuntu 20.04, and Ubuntu 22.04

  • Debian 10, and Debian 11

  • VMware Photon version 3, and Photon version 4  (supported, but not tested)

Upgrading from a Previous Version of VMware Aria Operations for Logs

Keep in mind the following considerations when upgrading to VMware Aria Operations for Logs 8.14.1.

Upgrade Path

You can upgrade to VMware Aria Operations for Logs 8.14.1 from version 8.12. If you have already upgraded from VMware Aria Operations for Logs 8.12 to version 8.14 or 8.14 with the Hotfix, we recommend that do not upgrade to version 8.14.1. The version 8.14 with the Hotfix resolves the same upgrade related issues that version 8.14.1 resolves.

Starting from VMware Aria Operations for Logs version 8.14.1, the upgrade process enables secure authenticated mode for inter-node communication. However, this mode is enabled only if the rolling upgrade is successful. It is not updated in case of a manual upgrade.

Important:

When you upgrade from the 8.12 version to 8.14.1, note that:

  • The upgrade process automatically restarts the clusters to enable secure authenticated inter-node communication in them.

  • The PRI and VERSION prefixes are not automatically added to raw logs in your log forwarding destination when you select the RAW Protocol. You must manually select the Adjust PRI/VERSION option to add these prefixes. See Add a Log Forwarding Destination to learn more. This option is a temporary accommodation to support certain configurations and will be phased out in future releases of the product to uphold the principle of raw forwarding.

Important Upgrade Notes

  • To upgrade to VMware Aria Operations for Logs 8.14.1, you must be running VMware Aria Operations for Logs 8.12.

  • When performing a manual upgrade from the command line, you must upgrade workers one at a time. Upgrading more than one worker at the same time causes an upgrade failure.

  • When you upgrade the primary node to VMware Aria Operations for Logs 8.14.1 from the user interface, a rolling upgrade occurs unless specifically disabled. ​

  • Upgrading must be done from the primary node's FQDN. Upgrading with the Integrated Load Balancer IP address is not supported.

  • VMware Aria Operations for Logs does not support two-node clusters. Add a third VMware Aria Operations for Logs node of the same version as the existing two nodes before performing an upgrade.

  • Photon OS has strict rules for the number of simultaneous SSH connections. Because the MaxAuthTries value is set to 2 by default in the /etc/ssh/sshd_config file, the SSH connection to your VMware Aria Operations for Logs virtual appliance might fail in the presence of multiple connections, with the following message: "Received disconnect from xx.xx.xx.xxx port 22:2: Too many authentication failures". You can use any of the following workarounds for this issue:

    • Use the IdentitiesOnly=yes option while connecting via SSH: #ssh -o IdentitiesOnly=yes user@ip

    • Update the ~/.ssh/config file to add: Host* IdentitiesOnly yes

    • Change the MaxAuthtries value by modifying the /etc/ssh/sshd_config file and restarting the sshd service.

  • The VM's SSH fingerprint is not preserved and changes after every upgrade, which might impact the appearance and user interface for users who connect using SSH. You must accept a new SSH fingerprint after the upgrade.

  • Any API traffic sent to a VMware Aria Operations for Logs instance on port 443 will be rejected. Although port 443 has never been declared for API traffic, it used to work before and will not work starting from version 8.10. Instead, use the recommended port 9543.

Internationalization Support

VMware Aria Operations for Logs 8.14.1 includes the following localization features:

  • The VMware Aria Operations for Logs web user interface is localized to Japanese, French, Spanish, German, Simplified Chinese, Traditional Chinese, and Korean.

  • The VMware Aria Operations for Logs web user interface supports Unicode data, including machine learning features.

  • VMware Aria Operations for Logs agents work on non-English native Windows.

Limitations

VMware Aria Operations for Logs 8.14.1 has the following limitations:

General

  • VMware Aria Operations for Logs does not handle non-printable ASCII characters correctly.

  • VMware Aria Operations for Logs does not support printing. However, you can use the Print options of your browser. The printed results might vary depending on the browser that you use. We recommend Internet Explorer or Firefox for printing portions of the VMware Aria Operations for Logs user interface.

  • The hosts table might display devices more than once with each in a different format, including some combination of IP address, hostname, and FQDN. For example, a device named foo.bar.com might appear as both foo and foo.bar.com.

    The hosts table uses the hostname field that is defined in the syslog RFC. If an event sent by a device over the syslog protocol does not have a hostname, VMware Aria Operations for Logs uses the source as the hostname. This might result in the device being listed more than once because VMware Aria Operations for Logs cannot determine if the two formats point to the same device.

  • Adding a new index partition or deleting an existing one requires a cluster restart (restarting cluster nodes one by one) for the new configuration to become effective. However, changes in the routing filter, enabled status, and retention period for existing index partitions apply immediately (restarting the cluster is not required).

  • Once activated, FIPS mode cannot be disabled.

VMware Aria Operations for Logs Windows and Linux Agents

  • Non-ASCII characters in hostname and source fields are not delivered correctly when VMware Aria Operations for Logs Windows and Linux agents are running in syslog mode.

VMware Aria Operations for Logs Windows Agent

  • The VMware Aria Operations for Logs Windows agent is a 32-bit application and all its requests for opening files from C:\Windows\System32 sub-directories are redirected by WOW64 to C:\Windows\SysWOW64. However, you can configure the VMware Aria Operations for Logs Windows agent to collect from C:\Windows\System32 by using the special alias C:\Windows\Sysnative. For example, to collect logs from their default location for the MS DHCP Server, add the following line to the corresponding section of the VMware Aria Operations for Logs Windows agent configuration file: =C:\Windows\Sysnative\dhcp.

VMware Aria Operations for Logs Linux Agent

  • Due to an operating system limitation, the VMware Aria Operations for Logs Linux agent does not detect network outages when configured to send events over syslog.

  • The VMware Aria Operations for Logs Linux agent does not support non-English (UTF-8) symbols in field or tag names.

  • The VMware Aria Operations for Logs Linux agent collects hidden files and directories by default. To prevent this, you must add an exclude=.* option to every configuration section. The option exclude uses the glob pattern .* which represents hidden file format.

  • When standard output redirection to a file is used to produce logs, the VMware Aria Operations for Logs agent might not correctly recognize event boundaries in such log files.

VMware Aria Operations for Logs Integrations

Launch in context, both from VMware Aria Operations for Logs and VMware Aria Operations, does not work for a virtual machine when the IP address of the virtual machine is not visible to the VMware Aria Operations instance and is not shown by the vCenter on the virtual machine's VM Summary tab. The IP address might be unavailable because of the absence of the vmware-tools utility. Older, unsupported versions or malfunctioning vmware-tools can also cause the IP address to become unavailable.

Ensure that a proper version of VMware Tools is installed on the virtual machine and that the VM Summary tab of the vCenter displays the IP address of the virtual machine.

Resolved Issues

Resolutions for the following issues are included in this release.

  • VMware Aria Operations for Logs cannot connect to a webhook server with a self-signed certificate.

  • You cannot integrate VMware Aria Operations for Logs with a webhook server that uses a self-signed certificate as the self-signed certificate is not trusted.

  • The triggered alert is listed in the history but not delivered to VMware Aria Operations and email.

  • After integrating the VMware Aria Operations for Logs 8.10.2 version with VMware Aria Operations, when you configure an alert, add extracted fields to the alert query, and trigger an alert, the alert is not delivered to the email recipients and to the VMware Aria Operations user interface.

  • The first token in the vCenter Server logs is truncated when forwarded from VMware Aria Operations for Logs using the Syslog format.

  • If the VMware Aria Operations for Logs forwarder is configured to use Syslog forwarding, the first token in the vCenter Server logs may be truncated at the forwarding destination.

  • The test alert sent to a webhook URL fails because of basic authentication issues.

  • When you create a webhook of Custom endpoint type, add basic authentication to the webhook, and then test the alert, the alert fails. This happens when the credentials are rejected because of basic authentication issues.

  • While attempting to import archived logs, the import process became stuck and never reached completion.

  • When you are importing a large number of archived events back into VMware Aria Operations for Logs, the standard log importer tool fails, and displays a message such as
  • failed to import parsed messages from 0 to 1000 in the /var/log/loginsight/importer.log file.
  • Additionally, the importer does not take into account disk blocks or ingestion speed.

Known Issues

The following known issues are present in this release.

  • Failure to save a configuration when there is a long list of filters in agent groups

  • VMware Aria Operations for Logs fails to process a long list of filters in agent groups and does not save any configuration because of this issue.
  • Workaround: Modify the internal configuration manually to remove or reduce the number of filters in the agent group or divide the filters into multiple agent groups.

  • VMware Aria Operations for Logs does not send more than 10 logs in webhook notifications.

  • Regardless of the Log Payload option, VMware Aria Operations for Logs sends only up to 10 individual notifications or 10 logs in the payload to the webhook endpoint.
  • Workaround: None.

  • Users are not notified about the cloud channel integration failure

  • You do not receive any notifications regarding failures related to cloud channel integration and cloud forwarding.
  • Workaround: Check the VMware Aria Operations for Logs runtime.log file for related issues, or check if the corresponding cloud organization is receiving the logs.

  • Inactive host notifications are sent when logs are relayed to VMware Aria Operations for Logs (SaaS)

  • In VMware Aria Operations for Logs, when you select the Inactive hosts notification check box on the Management > Hosts page, and select the Relay Only option while configuring log forwarding to VMware Aria Operations for Logs (SaaS), you receive inactive host notifications.
  • The value in the Last Received Event column in the Hosts page increases with time, which indicates that a previously active host does not ingest logs anymore.
  • This behavior is because log events are not considered received until the events are ingested. When you select the Relay Only option for cloud forwarding, a certain category of log events are never ingested (depending on your filter definition), which results in some hosts mistakenly reporting as non-ingesting and inactive.
  • Workaround: None.

  • The first run for real-time alerts is delayed

  • The first run for a real-time alert is scheduled five minutes after creating or enabling the alert.
  • Workaround: Wait for five minutes after creating or enabling a real-time alert for the scheduler to work as expected. After the first five minutes, the alert query is run every minute.

  • Collection from some of directories will not take place if they were created before agent start or re-configuration event

  • The logs are not collected from the newly created directories if you create the directories after re-configuring the agent.
  • Workaround: To start directory monitoring, restart the service or update the agent configuration. You can update the agent configuration using the liagent.ini file or from the Server Admin Agents page.

  • No automatic upgrade for VMware Aria Operations for Logs Agent on Photon OS

  • You cannot automatically upgrade VMware Aria Operations for Logs Agent on Photon OS because Photon OS does
  • not support the gpg command.
  • Workaround: Perform a manual upgrade.

  • SMTP configurations might not work for public mail servers through IPv6

  • SMTP configurations might not work with public email services such as Google and Yahoo, because these services leverage tighter restriction policies for IPv6.
  • Workaround: Use an alternative mail server such as your corporate mail server, or create a dedicated server.

  • Integrating VMware Workspace ONE Access with VMware Aria Operations for Logs through IPv4 changes the redirect URL host to IPv6 address

  • When deploying a VMware Aria Operations for Logs virtual appliance, If you had selected the option to prefer IPv6 addresses, the redirect URL host list is always populated with IPv6 node addresses. This redirect URL does not work when integrating VMware Aria Operations for Logs with VMware Workspace ONE Access as VMware Workspace ONE Access does not support IPv6 addresses.
  • Workaround: Create a different IPv4 virtual IP for the integration of VMware Aria Operations for Logs with VMware Workspace ONE Access.

  • Test connection fails for VMware Aria Operations for Logs Agent running on the Windows OS.

  • Test connection fails for VMware Aria Operations for Logs Agent running on the Windows OS, however the agent is able to successfully communicate and send logs to the VMware Aria Operations for Logs server.
  • Workaround: None
check-circle-line exclamation-circle-line close-line
Scroll to top icon