Documentation forLog Analyzer

LA 2019.4 Release Notes

Release date: November 5, 2019

These release notes describe the features in Log Analyzer (LA), formerly Log Manager for Orion, 2019.4. They also provide information about upgrades and describe workarounds for known issues.

Features and improvements in LA

LA is a fully-integrated log management solution that is accessible through your Orion Web Console. Upon installation, you can instantly view live event messages from nodes currently integrated with the Orion Platform, and quickly map unknown devices through the Node Management feature. Key benefits include live event filtering to target, identify, and alert on current network issues, and seamless transitions between critical event messages and associated Orion Platform products for on-the-spot troubleshooting and issue resolution.

New in LA 2019.4

The 2019.4 release includes minor bug fixes and enhancements. Learn more here.

LA 2019.4 is an Orion Platform product, and runs on Orion Platform 2019.4.

Localization improvements

Starting with LA 2019.4, you can use LA in German and Japanese. You can choose the language during a fresh install of an Orion server.

Additional LA features

Monitor Windows event logs

Starting with LA 2.0, you can stream, monitor, and alert on Windows event logs. From the LA Log Viewer, you can filter Windows events, enable out-of-the-box rules for events, and create custom rules tailored for specific Windows event activity.

Log forwarding

On the Log Processing Configuration page, create custom rules to forward your syslog and trap log messages to a dedicated server. This feature allows you to forward log data to third-party systems and other SIEM tools.

Additional poller support and Centralized Upgrades

Starting with LA 1.1.1, LA includes additional poller support and Centralized Upgrades. Learn more about additional poller engines here, and Centralized Upgrades here.

Orion alert integration

On the Log Processing Configuration page, you can integrate alert actions into your custom rules, or create new rules and apply alert actions. You can configure your rule to send an event to the Orion Platform alerting engine when the rule criteria are met, and also create a new alert that fires each time a rule is triggered.

For more information about Orion Platform alerting, see Create and manage alerts in the online LA Administrator Guide. To create a new rule in LA, see Create custom log-processing rules.

Before you upgrade

If you are adding LA 2019.4 to your existing Orion Platform products, make note of the following:

LA 2019.4 requires Microsoft SQL Server 2016 SP1 or later.

LA 2019.4 does not support data migration of existing rules and alerts.

Legacy syslog and traps

LA replaces the existing legacy syslog and trap services, but only provides a subset of the legacy functionality. After installation of LA over the legacy syslog and trap services, the records remain in the database, but will not be used by LA. You can still access the read-only legacy records in the Syslog Viewer and Traps Viewer applications. All new syslog and trap messages will be stored in the dedicated LA database.

Property changes to the Orion.OLM.LogEntryLevel entity

Please note that property changes to the Orion.OLM.LogEntryLevel entity may impact custom SWQL queries involving the SWIS/API (when using Orion SDK, Custom Reports, Custom SWQL Queries, Custom Resources).

Original properties Current properties
Name (String) Level (String)
Value (Int) LevelKey (String)

This change is related to localization. LevelKey contains the specific/static key, and Level contains the mapped or translated word for the string.

This issue impacts LA 2019.4 and Orion Log Viewer (OLV) 2019.4. This also impacts the following products when installed with OLV: NPM, NCM, SAM, VMAN, UDT, and the NAM/NOM bundles.

How to upgrade

Use the SolarWinds Orion Installer to upgrade one or more Orion Platform products simultaneously.

If you are upgrading from LA 1.1.1 or later, you can upgrade your entire Orion deployment, including the main server and all Orion Platform products, from the Settings > My Orion Deployment page. Downloading the Orion Installer is no longer necessary.

New customer installation

Use the SolarWinds Orion Installer, available in the Customer Portal, to install LA. After installation, refer to the LA Getting Started Guide to learn about configuring and customizing LA.

Fixed issues

LA 2019.4 fixes the following issues:

Case Number Description
00335052 00332128 00236041 Orion alerts are not triggering after an LA rule hit.
00338462 00334115 Custom rules are no longer available after upgrading.
00282351 Syslog messages from licensed Orion Platform nodes are dropped by LA.
00318625 00325743 00341858 00357350 LA and VMAN installed together causes database maintenance issues.
N/A The Configuration Wizard attempts to subscribe to SWIS.
00400032 Orion Log Viewer is not installed on additional polling engines.
00309775 Configuration Wizard fails due to an insufficient SQL database compatibility level.

Hotfixes

Known issues

Case Number Description
N/A High Availability shows Log Analyzer when only Orion Log Viewer is installed.
00394723 Menus fail to display due to intermittent database connections.
00386423 Database maintenance breaks for secondary source assignments.
N/A A TLS certificate cannot be used if it contains more than a CN field (OU, O, C, etc.).

Additional known issues

Log rules can be lost due to synchronization issues between websites

Issue: Rule edits made on the main poller are not reflected on the additional website, but if the same rule is subsequently edited on the additional website, it will overwrite the initial rule changes made on the main poller.

Workaround: If the rules are out of sync on different websites, restart the website (IIS) services.

Search does not work after migration to/from the Azure Managed Instance database

Issue: When a database is migrated from a local SQL Server to Azure Managed Instance and vice versa, searching for existing log entries may no longer work correctly due to a missing index in the database.

Workaround: Run the script in this article to enable indexes in existing tables and restore searching functionality.

Messages are dropped when changing Azure database tiers

Issue: With Microsoft Azure, messages are dropped when the Azure database tier is changed.

Workaround: Review this article for additional information.

Previous versions

LA 2.1

LA 2.0

LA 1.1.1

LA 1.1

LA 1.0

Legal notices

© 2019 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.