Licensing in SolarWinds NPM is typically managed how, and how does node count affect features?

Licensing in SolarWinds NPM is typically managed how, and how does node count affect features?

• A. Per-organization entitlement
• B. Per-node or per-probe; higher node counts provide broader coverage and advanced features; ensure licenses align with deployed modules (NPM, NTA, NetPath)
• C. Per-site license
• D. No licensing required for NPM

Answer: (B)

Licensing in SolarWinds NPM is based on the number of monitored nodes or probes, not per organization or per site. This means you buy a license that covers a specific count of devices or data sources you actively monitor. As you add more nodes, you need a higher node count license to keep monitoring and reporting without gaps. The number of nodes you license also influences which features you can access; expanding coverage often unlocks broader monitoring capabilities and, in some cases, higher-tier features. When you deploy multiple SolarWinds products, such as NPM, NTA, and NetPath, make sure your licenses include those modules so you’re entitled to use the features you’ve activated.

Licensing in SolarWinds NPM is based on the number of monitored nodes or probes, not per organization or per site. This means you buy a license that covers a specific count of devices or data sources you actively monitor. As you add more nodes, you need a higher node count license to keep monitoring and reporting without gaps. The number of nodes you license also influences which features you can access; expanding coverage often unlocks broader monitoring capabilities and, in some cases, higher-tier features. When you deploy multiple SolarWinds products, such as NPM, NTA, and NetPath, make sure your licenses include those modules so you’re entitled to use the features you’ve activated.