Submit a ticketCall us
Home > Success Center > Log Manager for Orion (LM) > Log Manager for Orion Documentation > SolarWinds Log Manager for Orion (LM) 1.0 Release Notes

SolarWinds Log Manager for Orion (LM) 1.0 Release Notes


Last updated: June 26, 2018

These release notes describe the features in LM 1.0. They also provide information about upgrades and describe workarounds for known issues.

LM features

LM 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 and identify current network issues, and seamless transitions between critical event messages and associated Orion Platform products for on-the-spot troubleshooting and issue resolution.

Filter and analyze event logs

In the LM Filters pane, select one or more filters to refine your event log stream to display messages based on event type, node, IP address, vendor, and more.

To drill down into a log summary for a specific node, click a node link in the Log Viewer table, and then click Analyze Logs in the Node Details Management pane.

Search and filter historical event logs

LM includes an advanced search capability to access your aggregated event logs based on applied filters and a specified range of time. To set your search parameters, select your log filters, and then on the histogram chart, open the custom time picker to set your time frame.

Filter and view event logs in live mode

Switch the Log Viewer to live mode to view events as they occur in your environment. This is particularly useful when troubleshooting active network problems. You can apply "live" filters to target and identify issues using the Filters pane and keyword search, and then observe the histogram chart to note any spikes in activity or log anomalies.

Create custom log-processing rules

On the Log Processing Configuration page, you can create custom rules to complement the standard, out-of-the-box LM rule sets. You can define rule conditions to identify a specific log entry, and then establish subsequent actions, such as adding event tags, executing commands, and discarding log entries.

Apply tags to event logs

Apply pre-defined and custom log tags to quickly identify specific log activity. For example, if you are interested in a certain event ID or keyword, you can configure your rule to display a color-coded tag notification on event logs matching the defined criteria. You can also apply multiple tags to a single log event ID or keyword.

Disable and enable log-processing rules

The Log Processing Configuration page includes out-of-the-box rules that provide a visual identifier for common event groups. These pre-defined log tags are enabled by default and allow you to quickly identify specific event activity in your Log Viewer table.

Monitor Orion Platform nodes in LM

Monitor any networked Orion Platform node in the LM Log Viewer with your LM license plan. In the Orion Web Console, check for available licenses by navigating to Settings > All Settings, and then clicking License Details in the Details pane. The License Details page lists all licensed Orion Platform products, including the total number of LM licenses, and the number of nodes currently consuming a license. For more licensing information, see the LM 1.0 Installation Guide.

To adjust your LM node settings, edit the node properties, and then select one of the LM monitoring options. For more information, see the LM 1.0 Getting Started Guide.

Add unknown nodes to the Orion Platform

In the Orion Platform, messages received from an unknown network node are discarded until you add the device through Node Management. When log activity is observed from an unknown device, you will receive a notification in the Orion Web Console linking you to the Events page, where you can add the node as a managed device.

Manually migrate existing NCM Real-Time Change Notification rules

You can apply existing NCM Real-Time Change Notification (RTCN) rules to your current LM log-processing rule set. When LM detects NCM RTCN rules, you will receive a notification in the Orion Web Console, which means you can then access and enable the rules through the LM Log Processing Configuration page. See the NCM RTCN article in the SolarWinds Customer Success Center for more information.

Drop unwanted event logs

Streamline your Log Viewer table by selecting and dropping unwanted event logs that clutter your log feed and occupy valuable database space. You can establish rule parameters that will discard all undesired logs to ensure relevant content displays in a more efficient manner.

Set LM storage and search retention period

On the Log Manager Settings page, you can set the number of days that syslog and traps messages are stored and searchable in the LM database. The default setting is seven days, but you can adjust it to anywhere from one day to one year.

Review unlicensed and unmonitored log source reports

You can access LM log source reports in the Orion Web Console by navigating to Reports > All Reports. In the Group By list, select Report Category, and then click Log Manager report. Each report lists the IP address and detection timestamp for unlicensed or unmonitored log sources.

Enable full-text search in Microsoft SQL Server 2016

When installing and configuring SQL Server 2016, enable full-text search to ensure optimum event log search performance within LM. You can still install LM and initiate event log searches without enabling this capability, but the speed and quality of your search may be significantly reduced.

Before you upgrade

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

  • LM 1.0 requires Microsoft SQL Server 2016 SP1 or later.
  • LM 1.0 does not support data migration of existing rules and alerts.

Legacy syslog and traps

LM replaces the existing legacy syslog and trap services, but only provides a subset of the legacy functionality (no alerting or data migration). After installation of LM over the legacy syslog and trap services, the records remain in the database, but will not be used by LM. 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 LM database. 

New customer installation

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

Fixed issues

LM 1.0 fixes the following issues:


LM does not show incoming syslog and traps messages when both LM and DPA are installed.


Add support for KIWI-specific IP address format.

  Orion Diagnostic doesn't gather OLM log files.
  Source Time not parsed correctly.
  Disabled rules are hard to identify.
  Configure Rules should be available only for administrators.
  Log Viewer history loading 2+ times on page load.
  Node changes are not propagated to the service immediately.


Configuration Wizard fails when NTA and Orion Logs are installed on same database.
  Configuration Wizard fails on Case Sensitive SQL Server.
  Re-running CW should not change enable/disable status.

Known issues

32-bit Microsoft Office products have issues after installing LM

Issue: As a part of the LM installation, the 64-bit Microsoft Access driver is installed. The installation of this driver causes issues with 32-bit Microsoft Office installations because Microsoft does not support side-by-side installations of 64-bit and 32-bit Office components. 

Workaround: Upgrade Microsoft Office to a 64-bit version before installing Orion Platform products. Find more information here.

Analyze Logs feature is available for disabled nodes

Issue: The Node Details page continues to display the Analyze Logs feature for disabled nodes when no log data is available.

Workaround: None. We expect to address the issue in a future version.

SNMP v3 credentials are not propagated to trap service immediately

Issue: When adding a node with SNMP credentials and then sending a trap message to LM with the credentials, the message is not immediately stored; it can take up to five minutes.

Workaround: None. We expect to address the issue in a future version.

The LM Viewer filter list is misaligned in IE11 and Microsoft Edge 

Issue: When syslog and trap messages stream into the Log Viewer, the Filters pane numbering and spacing are aligned incorrectly.

Workaround: None. We expect to address the issue in a future version.

Messages load slowly in the LM Log Viewer when using IE11

Issue: Messages in the LM Log Viewer load more slowly in IE11 than similar web browsers such as Chrome and Firefox.

Workaround: None. We expect to address the issue in a future version.

LM loses out-of-the-box rule status 

Issue: Enabled and disabled out-of-the-box rules may revert to their original setting after upgrading.

Workaround: None. Enable and disable rules where necessary.

Legal notices

© 2018 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.


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.



Last modified