Release Date: November 5, 2019
Updated January 10, 2020
These release notes describe new features, improvements, and fixed issues in SolarWinds Server & Application Monitor (SAM) 2019.4. They also provide information about installation, upgrades, and workarounds for known issues.
- For information about SAM hotfixes, click here.
- If you are looking for release notes for earlier SAM releases, see Previous Version documentation.
- To learn about requirements, see SAM 2019.4 System Requirements.
New features and improvements
Read this section to learn about new features and improvements offered in this release.
Simplified API monitoring for external REST API endpoints
You can use the new API Poller feature to monitor external REST APIs and gather metrics for nodes and applications in your environment, providing an easy way to collect data from a modern application stack in a simplified manner. Add an API poller, define API endpoints, determine available metrics, pick the values you want to monitor, and then begin monitoring without the need for custom scripts.
Using APIs as another data source for SAM monitoring enables you to:
- Gather additional metrics for nodes that can be used to troubleshoot Down nodes.
- Monitor applications with instances that are not yet monitored in SAM.
- Extract data from applications that are not traditional WMI- or SNMP-based applications, such as SaaS apps or public cloud services.
- Send API calls to update data in a remote API, such as device configurations. You can also send API calls to monitor HTTP response status codes.
For details, see Use API pollers to monitor metrics via remote APIs in SAM. For a video overview, see SolarWinds Lab #82 (Part 2).
Hardware health monitoring for Nutanix™ clusters
Monitor the hardware health of Nutanix clusters with the power of the Orion Platform, from alerting and reporting and mapping to AppStack™. With the latest release, you can:
- Check the status of Microsoft® Hyper-V and VMware® nodes in monitored Nutanix clusters.
- Display Nutanix hardware health data in the AppStack Environment.
- Use alerts and reports for Nutanix objects.
To get started, add Hyper-V or VMware nodes for monitoring, add the Nutanix cluster, and then provide Controller VM (CVM) credentials. For details, see Monitor hardware health for Nutanix clusters.
Documentation for Orion Platform features supported by multiple modules is included in the Orion Platform Administrator Guide. Because Nutanix monitoring is supported by both SAM and SolarWinds Virtualization Manager (VMAN), you'll find related details there.
Enhanced Microsoft Active Directory monitoring with domain trust support
For example, if you use SolarWinds AppOptics, a Software-as-a-Service (SaaS) product that allows deep dives into hybrid and cloud-native IT environments, you can configure an Active Directory trust that allows AppOptics to log into Active Directory resources hosted in a separate domain.
To support data collection for this new functionality, configure domain controllers with the Global Catalog (GC) role. Also, note that the AppInsight for Active Directory uses default port 3268 to gather trust data. If your domain controllers use port 3269, update that setting in the AppInsight for Active Directory template.
Orion Platform 2019.4: New features and improvements
Some of the new features and improvements provided in Orion Platform 2019.4 include:
- Microsoft Azure SQL Managed Instance support: Deploy the Orion Platform and modules in the cloud using an Azure Managed Instance as an alternative to MS SQL.
- Legacy Syslog and traps replacement: When you install SAM 2019.4 or later, you can replace legacy Syslog messages and SNMP traps with the Orion Log Viewer by installing an optional trial version of SolarWinds Log Analyzer (LA). To learn more, see:
- Orion Map improvements: Bulk- or multi-select entities to add them, add custom images, and define topology between entities directly in the Map Editor.
- Integration with SolarWinds Service Desk.
To learn more, see the Orion Platform 2019.4 Release Notes.
New customer installation
Use the Orion Installer, available in the Customer Portal, to install SAM. See the Orion Platform Products Installation and Upgrade Guide for details. After installation, see the SAM Getting Started Guide to learn about configuring and customizing SAM.
Before you upgrade
To prepare for the upgrade:
- Read these Release Notes.
- Make sure all servers comply with SAM 2019.4 System Requirements.
- (Optional) Back up any custom code, such as modified SolarWinds .css files or added .js files. Click here for tips.
Note the following details about upgrading SAM:
- Depending on options selected in the Orion Installer, the Orion Log Viewer replaces legacy Syslog and Traps with an instant evaluation of SolarWinds Log Analyzer (LA).
- Multiple application monitor templates were updated to support localization in a future release. Individual template updates are being added to THWACK, or you can download SAM_2019-4_Template_Updates.zip, save any custom changes made to existing templates, and then import the updated templates into SAM.
- To collect trust data for AppInsight for Active Directory, configure domain controllers as GC servers that use the default port, 3268. If your domain controllers use port 3269, update that setting in your AppInsight for Active Directory template.
- The Application Dependencies feature is disabled during upgrades to prevent performance issues for environments with large quantities of nodes. To restart polling after an upgrade, enable the Application Dependencies feature.
- If you exceed recommended cloud monitoring limits, you may receive a 503 Service Unavailable error when adding Azure accounts. Click here for a workaround.
- To monitor Exchange Server 2016 and later, install PowerShell 2.0 or later and provide local Administrator rights. See Using PowerShell in SAM.
- If using the container monitoring feature, rebuild containers after upgrading SAM and then add container services back into the Orion Platform. Click here for details.
SolarWinds recommends that you check THWACK periodically for updates to SAM's out-of-the-box (OOTB) templates. Apart from AppInsight templates, SAM doesn't update templates automatically during upgrades to avoid overwriting custom changes you may have made. For details, see Import and export SAM templates.
How to upgrade
If upgrading from SAM 6.9 or later, you can upgrade your entire Orion deployment from the My Orion Deployment page (Settings > My Orion Deployment). Downloading the Orion Installer is no longer necessary.
If you need to migrate SAM as part of your upgrade, see the Orion Platform Migration Guide.
|Orion Platform products that support cloud monitoring, including SAM, can now poll Azure VMs that were originally assigned to a Resource Group (instead of a Subscription) with access rights to application. Code was updated so if a subnet configuration moves to another Resource Group to which an application does not have access rights, machine data is updated and polling succeeds.|
|The Windows Update Monitoring template was updated to support Windows Server 2019 and resolve "Days passed from last Windows update" component monitor failure. Download the latest version from THWACK here.|
|A PowerShell script is now available to create SHA-256 certificates if you manually configure IIS servers for AppInsight for IIS. See Create self-signed SSL certificates for target IIS servers.|
An obsolete component monitor, Number of Detail Tables, was removed from the SolarWinds Network Traffic Analyzer Database template. Download the latest version from THWACK.
|The HTTPS Monitor was updated to support user-side certificate authentication. Now you can specify the X.509 certificate subject (also called a Distinguished Name or DN) from the local machine store instead of the current user store. Instead of using spaces or commas to separate subject fields, use only commas.|
AppInsight for Active Directory applications appear Down after disabling the Total Counters feature.
Issue: Replication polling requires a DNS or SysName value to compute replication for a destination domain controller FQDN name, but nodes configured for ICMP polling do not provide this data. As a result, AppInsight for Active Directory widgets may not reflect the actual status of ICMP nodes. Another impact is that replication widgets display IP addresses for ICMP nodes instead of assigned node names.
Workaround: Configure AppInsight for Active Directory nodes as Windows Servers that support both WMI and ICMP polling so that AppInsight for Active Directory widgets can display node status and names properly via WMI. Alternatively, edit the name of an ICMP node on the Node Details > Edit Properties page.
Application pools and websites on nodes monitored by AppInsight for IIS show Unknown status instead of Down status after being unmanaged.
Issue: After assigning AppInsight for IIS to a node, the application pools and websites exhibiting problem behavior could not be unmanaged in SAM. The status changed to Unknown but should appear as Down.
Workaround: Update the record in the Orion database. Click here for a workaround.
SSL Certificate Expiration widget doesn't show certificates for all bindings on IIS servers.
Issue: When AppInsight for IIS monitors a server that has two HTTPS site bindings with the same IP address and port, but different host names and SSL certificates, only the default certificate appears in the SSL Certificate Expiration widget.
Workaround: None. This issue is slated to be fixed in an upcoming SAM release.
Container monitoring stops after upgrade from SAM 6.7 or later.
Issue: YAML files need to be refreshed after the upgrade.
Workaround: Rebuild containers. Click here for details.
Days Remaining value in SSL Certificate Expiration and IIS SSL Certificate Expiration Report widgets are not updated for AppInsight for IIS.
Issue: Polling only occurs once — when AppInsight for IIS is assigned to a node — but does not continue.
Component monitor scripts in the AIX template do not execute if "Inherit credentials from node" is selected. This issue can impact CPU statistic, Paging statistic/sec, Percentage of using system devices, Disk operations/sec of system devices, and Top 10 active processes.
Issue: Header issues in Perl script output prevent component monitors from inheriting credentials from nodes, so scripts fail.
Workaround: Either edit component monitors to provide credentials, or avoid use of "Inherit credentials from node" for affected component monitors. Click here for details.
AppInsight for Active Directory performance counters appear as Unknown and may fail during SAM polling.
Issue: AppInsight for Active Directory looks for performance counters in the NT Directory Services (NTDS) category but some domain controllers store performance counters in the Directory Services category, a known Windows issue
Workaround: Rebuild Windows NTDS performance counters. Click here for details.
Application Dependency polling fails; application dependencies or connections between nodes for Windows Server and other applications do not appear as expected.
Issue: Rows in the dbo.AgentManagement_Agents table that share the same Node ID may cause an exception.
Workaround: Uninstall agents from nodes, remove duplicate rows in the database, and then reinstall agents. Click here for details.
The PowerShell version of the Server Clock Drift template returns invalid results and the following message: "Scripting Error: Script does not contain the expected parameters or is improperly formatted. 'Statistic' missing."
Issue: This may occur if the clock drift is small negative number, such as -0.001.
Workaround: This issue was fixed in SAM 6.4. If you started with a fresh install of SAM 6.4 or later, you should already have the updated template. If you began using an earlier version of SAM, download the latest version from THWACK here. You can also update the code in existing templates. Click here for details.
SQL Server locking causes the Orion database to grow after assigning the AppInsight for Active Directory template to nodes in SAM
Issue: SQL Server locks may occur if you exceed recommended limits for AppInsight for Active Directory monitoring; see Best practices for AppInsight for Active Directory. Locks can prevent rows from being deleted during daily database maintenance jobs, so the number of rows grows as polling continues.
Workaround: Delete rows from the database manually, or remove AppInsight for Active Directory from nodes, wait for daily database maintenance to finish, and then add AppInsight back to the nodes. Click here for details.
Application Dependency agent plug-in installation fails on Linux systems
Issue: Application Dependency agent plug-in deployment fails on 64-bit Linux systems and the following message on the Installed Agent Plug-Ins page: "Installation of 'Application Dependency Mapping - Linux x64' failed. Invalid argument Code [0x16]." This occurs because the owner of the plug-in file prevents the removal of the old version due to permission issues.
Workaround: Click here to view workarounds: One involves deleting a directory, /opt/SolarWinds/Agent/bin/Plugins/ADMProbe, before updating agents, and the other changes the owner of plug-in files.
In the Microsoft Azure App Service template, the Average response time component monitor that provides the average time taken for the app to serve requests is not working.
Workaround: Disable the component. This issue will be resolved in a future release.
End of life
See the End of Life Policy for details about life cycles for SolarWinds products.
|EoL Announcements||EoE Effective Dates||EoL Effective Dates|
July 31, 2019
End-of-Life (EoL) announcement – Customers on SAM 6.5 should begin transitioning to the latest version of SAM.
December 30, 2019
End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SAM 6.5 will no longer be actively supported by SolarWinds.
June 30, 2020
End-of-Life (EoL) – SolarWinds will no longer provide technical support for SAM 6.5.
March 12, 2019
End-of-Life (EoL) announcement – Customers on SAM 6.4 should begin transitioning to the latest version of SAM.
June 12, 2019
End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SAM 6.4 will no longer be actively supported by SolarWinds.
June 12, 2020
End-of-Life (EoL) – SolarWinds will no longer provide technical support for SAM 6.4.
April 6, 2018
End-of-Life (EoL) announcement – Customers on SAM 6.3 should begin transitioning to the latest version of SAM.
June 6, 2018
End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SAM 6.3 will no longer be actively supported by SolarWinds.
June 6, 2019
End-of-Life (EoL) – SolarWinds will no longer provide technical support for SAM 6.3.
See Currently supported software versions for more information.
© 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.