What's in the Release Notes

The notes cover the following topics:

• About vRealize Log Insight
• What's New
• Compatibility
• Limitations
• Upgrading from a Previous Release
• Internationalization Support
• Resolved Issues
• Known Issues

About vRealize Log Insight

vRealize Log Insight 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. vRealize Log Insight 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 vRealize Log Insight product documentation at  https://docs.vmware.com/en/vRealize-Log-Insight/index.html.

What's New

vRealize Log Insight 8.6.1 is a maintenance release with several fixes and a Photon kernel update.

Compatibility  

vRealize Log Insight 8.6.1 supports the following VMware products and versions:

• vRealize Log Insight can pull events, tasks, and alarms data from VMware vCenter Server 6.0 or later. In FIPS mode, vRealize Log Insight can be integrated with VMware vCenter Server 6.0 U1 or later.
• You can integrate vRealize Log Insight 8.6.1 with vRealize Operations 8.0.1 or later.
• vRealize Suite Lifecycle Manager 8.4.1 Product Support Pack 1 supports the installation of vRealize Log Insight 8.6.1. For more information, see the vRealize Suite Lifecycle Manager 8.4.1 Release Notes. To install and upgrade vRealize Network Insight by using vRealize Suite Lifecycle Manager, see the vRealize Suite Lifecycle Manager Installation, Upgrade, and Management Guide.

Browser Support

vRealize Log Insight 8.6.1 supports the following browser versions. More recent browser versions also work with vRealize Log Insight, but have not been validated.

• Mozilla Firefox 72.0 and above
• Google Chrome 78.0 and above
• Safari 11.1 and above
• Internet Explorer 11.0 and above
  Note: Internet Explorer Document mode must be used in Standards Mode. Other modes are not supported. The Compatibility View browser mode is not supported.

The minimum supported browser resolution is 1280 by 800 pixels.

Important: Cookies must be enabled in your browser.

vRealize Log Insight Windows Agent Support

The vRealize Log Insight 8.6.1 Windows agent supports the following versions:

• Windows 7, Windows 8, Windows 8.1, and Windows 10
• Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019

vRealize Log Insight Linux Agent Support

The vRealize Log Insight Linux agent supports the following distributions and versions:

• RHEL 5, RHEL 6, RHEL 7, and RHEL 8
• SUSE Enterprise Linux (SLES 11 SP3) and SLES 12 SP1
• Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, and Ubuntu 18.04
• VMware Photon, version 1 revision 2, version 2, and version 3

Limitations

vRealize Log Insight 8.6.1 has the following limitations:

General

• vRealize Log Insight does not handle non-printable ASCII characters correctly.
• vRealize Log Insight 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 vRealize Log Insight 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, vRealize Log Insight uses the source as the hostname. This might result in the device being listed more than once because vRealize Log Insight cannot determine if the two formats point to the same device.

• Adding a new data 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 data partitions apply immediately (restarting the cluster is not required).

• Once activated, FIPS mode cannot be disabled.

vRealize Log Insight Windows and Linux Agents

• Non-ASCII characters in hostname and source fields are not delivered correctly when vRealize Log Insight Windows and Linux agents are running in syslog mode.

vRealize Log Insight Windows Agent

• The vRealize Log Insight 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 vRealize Log Insight 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 vRealize Log Insight Windows agent configuration file: =C:\Windows\Sysnative\dhcp.

vRealize Log Insight Linux Agent

• Due to an operating system limitation, the vRealize Log Insight Linux agent does not detect network outages when configured to send events over syslog.
• The vRealize Log Insight Linux agent does not support non-English (UTF-8) symbols in field or tag names.
• The vRealize Log Insight 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 vRealize Log Insight agent might not correctly recognize event boundaries in such log files.

vRealize Log Insight Integrations

Launch in context, both from vRealize Log Insight and vRealize Operations, does not work for a virtual machine when the IP address of the virtual machine is not visible to the vRealize 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.

Upgrading from a Previous Version of vRealize Log Insight

Keep in mind the following considerations when upgrading to this version of vRealize Log Insight. 

Upgrade Path

You can upgrade to vRealize Log Insight 8.6.1 from 8.6 or 8.4.

Important Upgrade Notes

• To upgrade to vRealize Log Insight 8.6.1, you must be running vRealize Log Insight 8.6 or 8.4.
• 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 vRealize Log Insight 8.6.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.
• vRealize Log Insight does not support two-node clusters. Add a third vRealize Log Insight 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 connection. Because the MaxAuthtries value is set to 2 by default in the /etc/ssh/sshd_config file, the ssh connection to your vRealize Log Insight 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.

Internationalization Support

vRealize Log Insight 8.6.1 includes the following localization features.

• The vRealize Log Insight server web user interface is localized to Japanese, French, Spanish, German, Simplified Chinese, Traditional Chinese, and Korean.
• The vRealize Log Insight server web user interface supports Unicode data, including machine learning features.
• vRealize Log Insight agents work on non-English native Windows.

Limitations

• The agent installer and content pack are not localized. Parts of the vRealize Log Insight server Web user interface might still show non-localized strings and have layout issues.
• vRealize Log Insight is interoperable with localized versions of vCenter Server and vRealize Operations. However, Content Packs depend on matching non-localized log messages. vCenter Server events are retrieved in its default locale, which should be set to en_US. For more information, see http://kb.vmware.com/kb/2121646.
• Integration with Active Directory, vSphere, and vRealize Operations for user names with non-ASCII characters is not supported.
• Localization of event logs is not supported. Event logs support UTF-8 and UTF-16 character encoding only.

Resolved Issues

The following resolved issues are present in this release.

• Alert title displays source field name instead of value

  When you use the source field name in an alert title in the format ${source}, the resulting alert notification title displays "${source}" instead of the value of the source field.

• The upgrade from vRealize Log Insight 8.4 to 8.6 fails in the absence of an admin user

  The upgrade from vRealize Log Insight 8.4 to 8.6 may fail because of a previous removal of the built-in admin user from the system.

• Empty Alerts page

  The Alerts page may not list any alerts because of a corner case issue around the front-end parsing responses of the requests to fetch alert details.

• The root FS disk space is full

  The file auth.log does not not rotate correctly and takes up all the disk space in the root file system.

  Workaround: See https://kb.vmware.com/s/article/82170 for the workaround.

• Syslog events based on the RFC 822 timezone format do not appear on the destination side​

  Syslog events based on the RFC 822 timezone format (for example, '+0000') may get rejected or misinterpreted by destinations such as Splunk, IBM, and QRadar.

  Workaround: Upgrade to vRealize Log Insight 8.6.1, which uses an ISO 8601 compliant timezone (for example, '+04:00', 'Z') for syslog.

• Excessive API calls to vRealize Operations

  Excessive API calls are made to vRealize Operations when vRealize Log Insight tries to get information about non-existent resources in vRealize Operations.

• Webhook shims cannot parse webhook payloads

  Some webhook shims cannot parse webhook payloads because of character escaping in the payloads.

Known Issues

The following known issues are present in this release. 

• Virtual Center (VC) events collection is delayed

  After a restart of the vRealize Log Insight service or a cluster upgrade, Virtual Center (VC) events collection might be delayed if a large number of VC's are integrated.

  Workaround: Events are automatically restored as collected after a sufficient amount of time. The length of time depends on your environment. For example, for 80 VCs on a cluster with four nodes, the delay would be an hour.

• vRealize Log Insight cannot authenticate users and groups from a second trusted Active Directory when a two-way trust is configured

  When an Active Directory is configured with a two-way trust with another Active Directory, vRealize Log Insight cannot authenticate users and groups of the second trusted Active Directory. 

  Workaround: Use vIDM,  which is directly integrated with both Active Directories.

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

  If a new directory is being created after re-configuration of the Agent collection of newly created directories will not happen

  Workaround: To start directory monitoring, restart the service or update agent configuration with the liagent.ini file or from the Server Admin Agents page.

• No automatic upgrade for vRealize Log Insight Agent on Photon OS

  You cannot perform an automatic upgrade for vRealize Log Insight 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 e-mail services such as Google and Yahoo, because these services might leverage tighter restriction policies for IPv6. 

  Workaround: Use an alternative mail server such as your corporate mail server, or bring up a dedicated server.

• Integrating VMware Identity Manager with vRealize Log Insight through IPv4 changes the redirect URL host to IPv6 address

  If you select the option to prefer IPv6 addresses when you deploy a vRealize Log Insight virtual appliance, the redirect URL host list is populated by IPv6 node addresses while integrating with VMware Identity Manager, which does not support IPv6.

  Workaround: Create a spare IPv4 VIP for the integration of vRealize Log Insight with VMware Identity Manager.

• Layout issues in Internet Explorer 11.0 

  In Internet Explorer 11.0, there are layout issues for the user icon in the header and chart legend list display, on the Dashboards and Interactive Analytics tabs.

  Workaround: See https://kb.vmware.com/s/article/78592 for the workaround.

• The REST API call 'POST /api/v1/sessions' fails

  When you join a newly deployed node in vRealize Log Insight 8.2 or 8.3 with an old cluster upgraded from 4.8 or earlier, the REST API call 'POST /api/v1/sessions' to the new worker node fails and throws the following error:

  Error: write EPROTO 1319245176:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:

  You can find the relevant log in the REST client. Because of this error, you cannot get a session for the node.

  Workaround: Restart the vRealize Log Insight service by running the 'service loginsight restart' command on the affected node.

• vRealize Log Insight displays an "Upgrade unconfirmed" message even when the upgrade is successful

  While upgrading to vRealize Log Insight 8.4, a message stating that the upgrade status is unconfirmed might appear. This message does not have an impact on the overall upgrade status, and the upgrade is eventually successful.

  Workaround: None.

• vRealize Log Insight cannot connect to a webhook server with a self-signed certificate

  You cannot integrate vRealize Log Insight with a webhook server that uses a self-signed certificate, because the Trust On First Use (TOFU) pop-up window does not appear.

  Workaround: Add a self-signed certificate manually to the vRealize Log Insight virtual appliance and restart it.

  $ keytool -import -alias webhook -file <certificate> -keystore /usr/java/jre-vmware/lib/security/cacerts -storepass changeit
  $ service loginsight restart

• Strings in Alerts and vRealize Log Insight Cloud pages are not localized

  The text used in the pages of the Alerts tab and LI Cloud tab are available in English only, and are not localized.

  Workaround: None.

• No alert definitions for a vRealize Operations endpoint without integration permissions

  You cannot define an alert that has a vRealize Operations endpoint without integration permissions for vRealize Operations.

  Workaround: Assign the appropriate integration permissions to the role associated with the creator of the alert. On the Administration tab, under Management, click Access Control. On the Roles tab, modify the role and provide the Integrations > vRealize Operations > Edit permission to the role.

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

  When you create an alert with webhook notifications and send a test alert, the alert fails. This happens when the correct credentials are rejected because of basic authentication issues.

  Workaround: Add a custom header with the encoded username:password combination.