Documentation forServer & Application Monitor

SAM licensing model

Orion Platform products now support both perpetual licenses and subscription licenses. See License types in the Orion Platform documentation for details.

This section describes the two types of licensing available for SAM:

Additional topics include:

To upgrade from component-based licensing to node-based licensing, contact SolarWinds Sales.

Node-based licensing

Node-based licensing, available in SAM 6.9.1 or later, governs the number of managed nodes in your SAM environment, allowing you to monitor an unlimited number of component monitors on each managed node. In this context, the term "managed node" refers to any entity from which SAM extracts data directly via:

  • Supported polling methods such as SNMP, ICMP, or WMI,
  • Orion agents, or
  • API requests.

Typically, a managed node is a server, but can also be a VM, hypervisor, or Nutanix cluster, as well as an external node, API, or service.

If you monitor a VM directly, it counts as a managed node. However, individual VMs on a hypervisor do not count as managed nodes when performance metrics are gathered from the parent hypervisor. In that situation, the parent hypervisor is the managed node.

Count the number of managed nodes in your environment to determine the most suitable license tier.

SAM License Tiers
(node-based licensing)
Number of Managed Nodes
SAM10 10
SAM25 25
SAM50 50
SAM75 75
SAM100 100
SAM200 200
SAM300 300
SAM400 400
SAM500 500
SAM600 600
SAM700 700
SAM800 800
SAM900 900
SAM1000 1000
SAM1250 1250
SAM1500 1500
SAM2000 2000
SAM2500 2500
SAM3000 3000
SAM4000 4000
SAM5000 5000

*Additional tiers are available. Contact SolarWinds Salesfor details.

Add an Additional Polling Engine for SAM that does not require an extra license

With node-based licensing, you can add an Additional Polling Engine that does not require an extra license. By distributing polling away from the Main Polling Engine, you can improve your monitoring capacity, boost the Orion Web Console performance, and help ensure high availability.

Additional Polling Engines are also called "scalability engines." "Scalability engine" is a general term for any server that extends the monitoring capacity of your deployment, such as Additional Polling Engines (APEs), Additional Web Servers (AWS), or High Availability (HA) backups.

To add the APE after applying the main SAM license:

  1. Make sure you're using SAM 6.9.1 or later.
  2. Review APE port requirements.
  3. Run the SolarWinds Orion Installer to set up the APE.
  4. When prompted to select a Server Role, select the "Additional Polling Engine for Server & Application Monitor" option.

Note the following details about adding a SAM APE that doesn't require an extra license:

  • If you use other Orion Platform products that offer "included" APEs, the exact text for the Server Role varies. For example, if Storage Resource Monitor (SRM) is also installed, the option appears as "Additional Polling engine for Server & Application Monitor, Storage Resource Monitor."

  • The APE only polls for SAM and basic Orion Platform data such as node status and volume. For example, a SAM APE returns SAM data and basic node metrics, but doesn't return NPM node data such as interfaces.
  • You cannot use multiple licenses (also known as stacking) with SAM node-based licensing.

For tips about growing your SAM environment, see Scalability Engine Guidelines for SolarWinds products. You can also watch this short video (:58): Enterprise-class scalability of Orion products.

Component-based licensing

A component-based SAM license determines how many assigned component monitors you are allowed. As described in detail here, SAM application monitor templates contain multiple component monitors, each of which tracks a different statistic and consumes one license.

The value returned by a component monitor is a measurement of application health and availability that needs to be monitored. It can be a process, service, performance counter, port, URL, User Experience Monitor, Nagios script, or something similar. An application typically consumes 15 — 25 component monitors. The Windows Scheduled Task Monitor consumes 5 component monitors per Windows server.

You can use as many templates and component monitors as needed, as long as the number of assigned component monitors doesn't exceed the license count. If you exceed a license limit, component monitors beyond the limit are not activated and their statuses change to Not Licensed. Either disable assigned component monitors to reduce your total assigned monitor count, or upgrade your license. This also applies to API Poller metrics.

Asset Inventory data collection does not count against a component-based SAM license.

The following table lists component-based license levels.

SAM license tiers
(component-based licensing)
Number of monitored components
AL150 150
AL300 300
AL700 700
AL1100 1100
AL1500 1500
AL2500 2500
ALX Unlimited number of items to monitor standard polling throughput.

To verify the number of consumed and available component monitors, navigate to the SAM License Summary:

  1. Click Settings > All Settings.
  2. Under Product Specific Settings, click SAM Settings.
  3. Click SAM License Summary.

SAM licenses do not have to mirror the license count of other installed SolarWinds products. For example, you can install SAM with a 150-component license on an NPM server with an unlimited node license.

Verify the component monitors consumed per template

As described in detail here, each predefined SAM template includes one or more component monitors designed to monitor a server, application, or process. You can assign templates to nodes to create application monitors (sometimes called "applications) that are specific to that node. For most SAM application monitors, you can add or remove component monitors, or disable component monitors, as necessary. Each active component monitor in an application monitor counts against your license.

​Example: The Apache template includes 9 component monitors that retrieve server statistics from the built-in Apache server-status web page on Linux systems. If you have an AL150 license and assign all 8 component monitors in this template to a node, the balance of remaining licenses is 142 (150-8 = 142). If you assign only 5 of the 8 component monitors to a node, the balance of remaining licenses is 145 (150-5=145).

To view the number of licensed component monitors consumed per template in SAM:

  1. Click Settings > All Settings > SAM Settings.
  2. Under Product Specific Settings, click SAM Settings
  3. Under Application Monitor Templates, click Manage Templates.
  4. Review the Licensed Components column amount per template.

AppInsight applications consume licenses at flat rates

Note that AppInsight applications consume a fixed number of component monitor licenses; you cannot add component monitors and many component monitors cannot be disabled. Due to the complex AppInsight templates that these application monitors are based on, they cannot be partially unlicensed because the way they collect data differs significantly from traditional SAM templates.

Although you can disable some components within AppInsight applications, that won't reclaim component monitor licenses because AppInsight applications typically monitor far more components than cited in their flat rates, as listed here:

  • AppInsight for Active Directory: 50 component monitors per monitored domain controller
  • AppInsight for Exchange: 50 component monitors per monitored mailbox role server
  • AppInsight for IIS: 30 component monitors per monitored IIS server
  • AppInsight for SQL: 50 component monitors per database instance

If you choose not to use AppInsight applications, you are not penalized any number of component monitors.

Determine your SAM license type

To check which type of license you have:

  1. Click Settings > All Settings > License Details.
  2. Examine the SAM section of the License Details page:

You can also check your license type in the SolarWinds Customer Portal.

  1. Log into the SolarWinds Customer Portal.
  2. Click Licenses > Manage Licenses.
  3. Scroll down to the Server & Application Monitor row.

If a license starts with SAM (for example, SAM200), SAM uses a node-based license.

If a license starts with AL (AL2500), SAM uses a component-based license.

Manage your SAM license

Like other Orion Platform products, SAM uses the web-based License Manager to license the Orion server, Additional Polling Engines, Additional Web Servers, and High Availability (HA) pools.

To manage SAM and other licenses after you install SAM:

  1. Click Settings > All Settings.
  2. Click License Details in the Details section.

  3. Click License Manager.

You can sort licenses by product name, version, license type, or expiration date. You can also add a license, upgrade a license to a new tier, and activate licenses on new servers. The License Manager on the Orion server controls all licenses for your SAM environment, including licensing for scalability engines.

If prompted to activate your SAM license, use your individual Customer ID (also called a "SWID") to log into the SolarWinds Customer Portal. If you do not know your Customer ID, enter a Support ticket.

Still have questions? Visit the SolarWinds Success Center and review SAM Licensing FAQs.