cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 7

How are licenses consumed in SAM?

Jump to solution

I am still confused regarding license consumption with SAM.  The installation of Solarwinds we use has the following modules and licensing levels.

NCM - 500

NPM - 2000

IPAM - Unlimited

We want to purchase SAM and are trying to determine the appropriate license level we have approximately 300 servers.  Want to monitor services on the DHCP, Print, account lockout on DC's. 

My question is this....I apply a template to a node the template is already monitored via NPM.... The template has 10 component monitors would the license consumption be as follows:

  • 1 node X 1 Template (10 component monitors) = 10 licenses used
0 Kudos
1 Solution
Level 15

http://www.solarwinds.com/documentation/en/flarehelp/sam/default.htm#OrionAPMAGLicensing.htm

Licensing

The SolarWinds SAM license you purchase is based on the number of allowed assigned component monitors. A component monitor provides a statistic that you want to monitor in SolarWinds SAM. You can have as many application templates and assigned monitors as you need, as long as the number of assigned component monitors does not exceed the license count.

If you have more assigned component monitors than allowed by your license, the monitors that exceed your license limit are not activated, and their component statuses are changed to "Not Licensed." You can either disable some assigned component monitors to reduce your total assigned monitor count, or contact SolarWinds about upgrading your SolarWinds SAM license.

table.png

Asset Inventory data collection

Asset Inventory data collection does not count against your SAM component monitor license.

Windows Scheduled Task Monitor

The WSTM consumes five (5) license units per node.

AppInsight for SQL

When using AppInsight for SQL, 50 component monitors will count against your licensed number of component monitors, per SQL instance.

AppInsight for Exchange

When using AppInsight for Exchange, 50 component monitors will count against your licensed number of component monitors, per Exchange Server.

View solution in original post

0 Kudos
2 Replies
Level 15

http://www.solarwinds.com/documentation/en/flarehelp/sam/default.htm#OrionAPMAGLicensing.htm

Licensing

The SolarWinds SAM license you purchase is based on the number of allowed assigned component monitors. A component monitor provides a statistic that you want to monitor in SolarWinds SAM. You can have as many application templates and assigned monitors as you need, as long as the number of assigned component monitors does not exceed the license count.

If you have more assigned component monitors than allowed by your license, the monitors that exceed your license limit are not activated, and their component statuses are changed to "Not Licensed." You can either disable some assigned component monitors to reduce your total assigned monitor count, or contact SolarWinds about upgrading your SolarWinds SAM license.

table.png

Asset Inventory data collection

Asset Inventory data collection does not count against your SAM component monitor license.

Windows Scheduled Task Monitor

The WSTM consumes five (5) license units per node.

AppInsight for SQL

When using AppInsight for SQL, 50 component monitors will count against your licensed number of component monitors, per SQL instance.

AppInsight for Exchange

When using AppInsight for Exchange, 50 component monitors will count against your licensed number of component monitors, per Exchange Server.

View solution in original post

0 Kudos
Level 17

Using NPM SL500 and SAM AL700 as example license tiers, you will end up with 1200 nodes, 1200 volumes, 500 interfaces and 700 component monitors. The nodes and volumes are additive, and these are reflected in the Settings > License Details page. A node element is consumed only once. If you have a node already monitored in NPM, and now want to apply a SAM template there is no additional node element license consumption. Only the component monitors in the template get deduced from the license usage. In your example, 10 - so you will still have 690 component monitors to use. What about hardware health of the server, real-time process explorer, service control manager, real time event log viewer - well, they are all covered by the single node element. 

One additional unsolicited information - If you had a Windows node in NPM and if you were monitoring interfaces usin SNMP today - upon purchasing SAM if you switch the polling method to WMI, the interfaces on these nodes are automatically monitored by SAM simply by virtue of the node license and those interface elements should get freed up from the 500.