SolarWinds · Solutions Engineering · APJ

SolarWinds Observability SaaS
License & Sizing Calculator

Size a full-stack SolarWinds Observability SaaS subscription across all modules — Network, Infrastructure, Application (APM), Database, Digital Experience (Synthetics & RUM), and Logs — using the à-la-carte, entity/consumption-based model. This calculator returns licensable quantities only (no pricing). Because the SaaS backend is hosted by SolarWinds, the only customer-side "hardware" to size is the collectors and agents that ship telemetry to the cloud.

Monitoring scope (entities)

How SaaS licensing counts things: each module is licensed separately by the number of active entities (or consumption) monitored in the previous calendar day. Smaller resources share an entitlement — VMs 3:1, cloud services 3:1, containers & wireless APs 10:1. ICMP-only status nodes are included free.

Network & Infrastructure Observability

Routers, switches, firewalls (1:1).

10 share 1 entitlement.

Agent or collector (1:1).

VMware/Hyper-V/Nutanix host (1:1).

3 share 1 entitlement.

AWS/Azure services, 3:1.

10 share 1 entitlement.

1:1.

Drives dedicated flow collector sizing (≤40,000 FPS each).

Applications & Databases

Per active service, any # instances.

Per active instance.

Digital Experience — Synthetic Uptime

Uptime checks = endpoints × locations × protocols. e.g. 20 endpoints × 2 locations × 1 protocol = 40 uptime checks. Each private probe you deploy counts as an additional location, so private probes are added to the location count before multiplying.

Distinct targets to monitor.

e.g. HTTP(S), TCP, ICMP, DNS.

SolarWinds cloud test locations.

Agent-based probes hosted inside the customer network for internal endpoints.

Digital Experience — Transactions & RUM

Scripted multi-step journeys. 2 / bundle (5 checks each).

Bundles of 100,000 pageviews.

Logs

Priced per GB/day; org ceiling ≈ 200 GB/hr.

Network & Infrastructure entitlements iWeighted network + infrastructure entitlements — the primary SWO SaaS sizing metric. Per-module quantities are broken out below.
—
Quantity estimate · confirm in CPQ
Network & Infrastructure iWeighted entitlements: network devices + APs÷10; hosts + hypervisors + VMs÷3 + cloud÷3 + containers÷10 + storage.
—
Applications & Databases
—
Digital Experience
—
Logs
—

Contact us

Product Manager Vera Pratiwi Vera.Pratiwi@westcon.com
Sales Engineer Teguh P. Mulyo teguh.mulyo@westcon.com

Module license summary

Licensable quantities for active modules only. Confirm all quantities in CPQ.

ModuleUnit of measureQuantity

Collectors & agents — Minimum vs Recommended

1 · Minimum

Documented minimum collector spec

ComponentQtyCPURAMStorage

2 · Recommended

Recommended spec + HA / redundancy

ComponentQtyCPURAMStorage

Entity weighting & units of measure

ModuleEntity / unitCounts as
NetworkNetwork device (router/switch/firewall)1:1
NetworkWireless access point10:1
InfrastructureHost / server (agent or collector)1:1
InfrastructureHypervisor / virtual host1:1
InfrastructureStandalone VM3:1
InfrastructureCloud service (AWS/Azure, non-host)3:1
InfrastructureKubernetes container10:1
InfrastructureStorage array1:1
InfrastructureICMP-only status nodeFree
APMApplication service (any # instances)Per service
DatabaseDatabase instancePer instance
DEM — Synthetic UptimeUptime check = endpoint × location × protocol10 uptime checks / bundle
DEM — Synthetic TransactionsScripted transaction (5 checks each)2 transactions / bundle
DEM — RUMPageviewsPer 100,000 / month
LogsLog ingestionPer GB (monthly plan)

How this is calculated

  • SolarWinds Observability SaaS uses an à-la-carte, modular subscription: each capability area is licensed independently by active entities or consumption measured in the previous calendar day.
  • Network & Infrastructure (NICO) is priced by active network devices and infrastructure hosts. Weighting: network device / hypervisor / host / storage array 1:1; wireless AP & container 10:1; standalone VM & cloud service 3:1. When one device is monitored via multiple channels it counts once; ICMP-only status nodes are free.
  • APM is per active service (independent of the number of running instances). Database is per active instance. RUM is per 100,000 pageviews/month. Synthetics is licensed in bundles of 10 checks — a bundle holds either 10 uptime checks or 2 scripted transactions. Uptime checks are derived as endpoints × locations × protocols (e.g. 20 endpoints × 2 locations × 1 protocol = 40 uptime checks); when private probes are used, each private probe adds to the location count before multiplying. Logs is a monthly plan measured per GB ingested.
  • No customer backend to size — storage, processing, and the web application are hosted by SolarWinds. Customer-side sizing covers only collectors and agents: the Network Collector (≤7,000 standard devices each; min 4 CPU/16 GB, rec 8 CPU/32 GB, 40 GB + SQL), the lightweight per-host SolarWinds Observability Agent (OTLP 443, no central server), the SWO K8s Collector for clusters, and optional dedicated flow collectors (≤40,000 flows/sec each). APM libraries and RUM run in-app; synthetics use SolarWinds public probes (or optional agent-based private probes).
Sources

Indicative SE quantity-sizing estimate for SolarWinds Observability SaaS. Entity weighting, module tiering, and collector counts must be validated in CPQ and against current SolarWinds Observability SaaS system-requirements and subscription documentation before quoting.

SolarWinds · Solutions Engineering · APJ

OSH Essentials & Advanced
License & Hardware Sizing Calculator

Size the SolarWinds Observability Self-Hosted (OSH) Essentials or Advanced tier from monitored node capacity, then derive minimum and recommended self-hosted hardware. Both tiers use simple node-based licensing and scale through Standard and Enterprise editions. Poller sizing follows the 2026 scalability guide — per-poller capacity is protocol-dependent, not a flat element count.

Licensing inputs

Essentials: NPM, SAM, LA, IPAM, UDT, VNQM & Cloud. Advanced adds NTA, NCM, VMAN, SCM, anomaly-based alerting & the security vulnerability dashboard.

How licensing counts nodes: most monitored devices consume one node license each. ICMP-only status nodes (ping availability) are free, and cloud/hypervisor-discovered VMs are free until you assign additional monitoring — then each counts as one full node. Value-based fractional licensing is a Premier-only feature and does not apply to Essentials or Advanced.

Servers, network devices, wireless controllers, autonomous APs, and any node with monitoring beyond ICMP status. Exclude ICMP-only status nodes (free).

Standard scales up to 1,500 nodes. Enterprise is required beyond 1,500 nodes and whenever Additional Polling Engines (APEs) are needed.

Self-Hosted (OSH) polling workload

Sets per-poller element capacity: SNMPv2 100k · SNMPv3 72k · WMI/WinRM 20k (max 2,000 nodes), at 16 cores.

Interfaces, volumes, apps, component monitors per node. Typical 8–12.

40k / APE.

1,000 / poller.

50k FPS / poller. Requires Advanced (NTA).

25–50 / web server.

Recommended license tier iSmallest published node tier covering total required capacity for the selected OSH tier. CPQ rounds up to the next valid tier.
—
—
Total required capacity iLicensed nodes + planned additions, then + growth headroom %.
—
Scale edition iStandard up to 1,500 nodes (includes additional web servers; HA is an add-on). Enterprise required above 1,500 nodes or for APEs; adds APEs, HA, EOC, lab licenses & Advanced Support.
—
Polling engines required iMaximum across workload dimensions: elements ÷ protocol capacity, SAM components ÷ 40k, flows ÷ 50k FPS, agents ÷ 1,000, and WMI's 2,000-node cap. APEs require an Enterprise license.
—
Additional web servers iThe main server hosts the Web Console for up to ~50 concurrent users; add web servers for more. Included in both Standard and Enterprise.
—

Contact us

Product Manager Vera Pratiwi Vera.Pratiwi@westcon.com
Sales Engineer Teguh P. Mulyo teguh.mulyo@westcon.com

Module coverage by tier

Selected tier highlighted. Advanced includes everything in Essentials plus the additional capabilities below.

CapabilityEssentialsAdvanced

Additional Polling Engines (APEs), Enterprise Operations Console (EOC), and lab licenses require the Enterprise edition of either tier. High Availability is available as an add-on on Standard.

Published node tiers

Matching tier highlighted. Standard up to 1,500 nodes; Enterprise from 500 and required beyond 1,500.

EditionAvailable node tiers
Standard
Enterprise

Self-Hosted infrastructure — Minimum vs Recommended

1 · Minimum hardware

Self-Hosted (OSH)
ComponentQtyCPURAMStorage

2 · Recommended hardware

Self-Hosted (OSH)
ComponentQtyCPURAMStorage

Per-poller scalability limits (2026 guide)

DimensionPer polling enginePer instance
Elements — SNMPv2100,000 (16 cores; +7,500/core → max 150,000)1,000,000 elements · 100 APEs
Elements — SNMPv372,000 (16 cores; +5,000/core → max 100,000)
Elements — WMI/WinRM20,000 (max 2,000 nodes; +2,000/core → 30,000)
SAM component monitors40,000 (APE) · ~10,000 (main)550,000
NetFlow (NTA) — Advanced50,000 flows/sec300,000 flows/sec
SolarWinds agents1,000 (−10 per remote collector)—
UDT ports100,000500,000
VMAN VMs — Advanced10,000 (per APE)—
Web console users25–50 per web server50–100 (main)

How this is calculated

  • OSH Essentials and Advanced use simple node-based tier licensing. ICMP-only availability nodes are free; a node becomes billable once additional monitoring (apps, interfaces, NCM profiles, or other services) is enabled. Cloud/hypervisor-discovered VMs are free until additional monitoring is assigned, then count as one full node.
  • Essentials includes NPM, SAM, LA, IPAM, UDT, VNQM and cloud monitoring. Advanced adds flow monitoring (NTA), NCM, VMAN, SCM, ML anomaly-based alerting, and the security vulnerability dashboard. WPM, SRM, Incident Response and the attached SWO SaaS (NICO) license are Premier-only and are not included here.
  • Value-based (fractional) licensing and license overages/bursting are Premier-only features and are excluded from this Essentials/Advanced sizing.
  • Scale edition: Standard includes additional web servers and allows HA as an add-on but does not include APEs. If sizing needs one or more APEs, or capacity exceeds 1,500 nodes, an Enterprise license is required. Enterprise also bundles HA, EOC, lab licenses and Advanced Support.
  • Polling engine count is the maximum across workload dimensions: elements ÷ protocol capacity (SNMPv2 100k / SNMPv3 72k / WMI 20k, at 16 cores), SAM components ÷ 40,000, flows ÷ 50,000 FPS (Advanced only), agents ÷ 1,000, and WMI's 2,000-node cap. Each instance supports up to 100 APEs and 1,000,000 elements.
  • Server hardware tiers (CPU/RAM) follow SolarWinds Platform 2026.2 system requirements; element-heavy pollers need 16 cores to reach the protocol caps, and more cores raise the cap further. Recommended adds a headroom tier plus redundancy: an HA database pair, an extra APE, and an additional web server.
Sources

Indicative SE sizing estimate for OSH Essentials and Advanced. Licensing, module coverage, protocol mix and final hardware must be validated in CPQ and against the customer's live license report and current 2026 system-requirements / scalability documentation before quoting.

SolarWinds · Solutions Engineering · APJ

OSH Premier
License & Hardware Sizing Calculator

Size the SolarWinds Observability Self-Hosted (OSH) Premier tier from monitored capacity, then derive minimum and recommended hardware for the self-hosted platform and the SaaS side (network collectors and per-host agents). Poller sizing follows the 2026 scalability guide — per-poller capacity is protocol-dependent, not a flat element count.

Licensing inputs

How licensing counts things: most devices use 1 full license each. Smaller resources share a license — cloud VMs 3-to-1, containers & thin wireless APs 10-to-1. Enter each type in its own field; sharing is applied automatically.

Servers, network devices, wireless controllers, autonomous APs, paid ICMP nodes. Exclude ICMP-only status nodes (free).

3 share 1 node.

10 share 1 node.

10 share 1 node.

Included components (Tier 2 · no node impact in 2026.2)

Self-Hosted (OSH) polling workload

Sets per-poller element capacity: SNMPv2 100k · SNMPv3 72k · WMI/WinRM 20k (max 2,000 nodes), at 16 cores.

Interfaces, volumes, apps, component monitors per node. Typical 8–12.

40k / APE.

1,000 / poller.

50k FPS / poller.

25–50 / web server.

SaaS monitoring scope

Agentless via Network Collector — up to 7,000 standard devices each.

Per-host agent.

Via collector.

≤40,000 flows/sec per collector.

Recommended Premier tier iSmallest published Premier node tier covering total required capacity. CPQ rounds up to the next valid tier.
—
—
Total required capacity iFull nodes + additions + cloud (÷3) + containers (÷10) + thin APs (÷10), then + growth headroom %.
—
Attached SaaS capacity iSWO SaaS (NICO) network/infra quantity aligns 1:1 with the Premier quantity.
—
Aligned 1:1 with Premier nodes
Overage headroom iAdds 25% of the license or 500 nodes, whichever first. Requires SWIP + outbound connectivity.
—
Enable overage to calculate burst
Storage / WPM (included) iWPM & SRM are included & unlimited in Premier today (Silicon 2026.2) and do not consume nodes. From Tungsten 2026.4, SRM is planned at ~5 nodes/array.
Included
Incident Response iIR Pro is bundled; included user count is set by the Premier tier. Extra users add independently at cost.
Bundled

Contact us

Product Manager Vera Pratiwi Vera.Pratiwi@westcon.com
Sales Engineer Teguh P. Mulyo teguh.mulyo@westcon.com

Published Premier node tiers

Matching tier highlighted. Standard up to 1,500 nodes; Enterprise from 500 and required beyond 1,500.

EditionAvailable node tiers
Standard
Enterprise

Infrastructure — Minimum vs Recommended

1 · Minimum hardware

Self-Hosted (OSH)
ComponentQtyCPURAMStorage
SaaS side
ComponentQtyCPURAMStorage

2 · Recommended hardware

Self-Hosted (OSH)
ComponentQtyCPURAMStorage
SaaS side
ComponentQtyCPURAMStorage

Per-poller scalability limits (2026 guide)

DimensionPer polling enginePer instance
Elements — SNMPv2100,000 (16 cores; +7,500/core → max 150,000)1,000,000 elements · 100 APEs
Elements — SNMPv372,000 (16 cores; +5,000/core → max 100,000)
Elements — WMI/WinRM20,000 (max 2,000 nodes; +2,000/core → 30,000)
SAM component monitors40,000 (APE) · ~10,000 (main)550,000
NetFlow (NTA)50,000 flows/sec300,000 flows/sec
SolarWinds agents1,000 (−10 per remote collector)—
SRM LUNs40,000160,000
UDT ports100,000500,000
VMAN VMs10,000 (per APE)—
Web console users25–50 per web server50–100 (main)
SaaS Network Collector7,000 standard devices · 40,000 flows/secdeploy multiple

How this is calculated

  • Premier uses node-based tier licensing and scales like Essentials/Advanced; ICMP-only nodes are free until additional monitoring is enabled. Cloud VMs ~3:1, containers ~10:1, thin APs 10:1 (confirm against the live license report).
  • WPM & SRM are included and unlimited in Premier today (Silicon 2026.2) and do not consume nodes; from Tungsten 2026.4, SRM is planned at ~5 nodes/array. IR Pro is bundled by tier; SaaS (NICO) aligns 1:1.
  • OSH poller count is the maximum across workload dimensions: elements ÷ protocol capacity (SNMPv2 100k / SNMPv3 72k / WMI 20k, at 16 cores), SAM components ÷ 40,000, flows ÷ 50,000 FPS, agents ÷ 1,000, and WMI's 2,000-node cap. Each instance supports up to 100 APEs and 1,000,000 elements.
  • Server hardware tiers (CPU/RAM) follow SolarWinds Platform 2026.2 system requirements; element-heavy pollers need 16 cores to reach the protocol caps, and more cores raise the cap further.
  • SaaS network devices are sized by the Network Collector (≤7,000 standard devices each; a standard device is SNMPv2 with ~15 interfaces). SaaS servers are monitored by the per-host Observability Agent (no central server; sends via OTLP 443) or agentlessly through a collector. Flow monitoring is ≤40,000 flows/sec per collector.
  • Recommended adds a headroom tier plus redundancy: HA database pair, an extra APE, an additional web server, and a standby / dedicated flow collector.
Sources

Indicative SE sizing estimate. Pricing, value-based licensing weights, protocol mix, and final hardware must be validated in CPQ and against the customer's live license report and current 2026 system-requirements / scalability documentation before quoting.

SolarWinds · Solutions Engineering · APJ

Database Performance Analyzer (DPA)
License & Server Sizing Calculator

Size a SolarWinds DPA deployment from the number of monitored database instances. DPA is licensed per monitored database instance — current subscription licenses are DBSH (Database Self-Hosted, any edition of any supported database, VM metrics included) and DBSHDS (Database Self-Hosted DBaaS). Server and repository hardware follow the DPA 2026.2 system requirements, bracketed by instances per DPA server (max 250 each).

Licensing inputs

How DPA licensing counts: one license per monitored database instance. DBSH covers any edition of SQL Server, Oracle, MySQL, MariaDB, PostgreSQL, Db2, SAP ASE & HANA (cloud-hosted equivalents included) and bundles VM metrics — no VM Option needed. DBSHDS covers DBaaS targets such as Azure SQL Database. Licenses float: register more instances than licenses and assign them on the allocation page.

SQL Server, Oracle, MySQL, MariaDB, PostgreSQL, Db2, SAP ASE/HANA — incl. RDS, Aurora, Cloud SQL, Azure MI. 1 license each.

Azure SQL Database and other supported DBaaS targets. 1 license each.

Server sizing workload

Registering VMware raises DPA server CPU & RAM needs by ~50%.

Only relevant with multiple DPA servers. DPA Central links servers into one view; co-locate it on a monitoring DPA server.

Total DPA licenses required iMonitored instances + planned additions, then + growth headroom %. One license per monitored database instance.
—
Per monitored DB instance · confirm in CPQ
DBSH licenses iDatabase Self-Hosted — any edition of any supported database type; VM metrics included.
—
DBSHDS licenses iDatabase Self-Hosted DBaaS — supported DBaaS targets such as Azure SQL Database.
—
DPA servers required iOne DPA server monitors up to 250 instances. Beyond that, add servers and link them with DPA Central.
—
Deployment bracket iSystem-requirements bracket per DPA server: 1–20, 21–50, 51–100 or 101–250 monitored instances.
—

Contact us

Product Manager Vera Pratiwi Vera.Pratiwi@westcon.com
Sales Engineer Teguh P. Mulyo teguh.mulyo@westcon.com

License summary

Licensable quantities for the current scope. Confirm all quantities in CPQ.

LicenseUnit of measureQuantity

DPA server & repository — Minimum vs Recommended

1 · Minimum hardware

ComponentQtyCPURAMStorage

2 · Recommended hardware

ComponentQtyCPURAMStorage

Repository RAM is shown as the database cache dedicated to DPA. Repository runs on SQL Server (Std/Ent), MySQL, Oracle or Azure SQL Database (Std tier+); Azure SQL Managed Instance is not supported as repository. Installing DPA on the repository server means meeting both spec sets combined.

License types

LicenseStatusCoverage
DBSH — Database Self-HostedCurrent subscriptionAny edition of any supported database type (SQL Server, Oracle EE/SE/XE, MySQL, MariaDB, PostgreSQL/EDB, Db2, SAP ASE, SAP HANA, incl. RDS/Aurora/Cloud SQL/Azure equivalents). VM metrics included — no VM Option needed.
DBSHDS — DBSH DBaaSCurrent subscriptionSupported DBaaS targets, such as Azure SQL Database.
Category 1 / Category 2Legacy (≤ DPA 2024.3)Edition-based: Cat 1 required for Oracle EE & SAP ASE; Cat 2 covers Express/lower-tier editions and Azure SQL DB. No functional difference between categories.
Azure SQL DatabaseLegacy (≤ DPA 2024.3)Azure SQL Database instances.
VM OptionLegacy (≤ DPA 2024.3)Add-on to Cat 1/Cat 2 for VM & host metrics (Virtualization view).

DBSH & DBSHDS keys are shared with SQL Sentry — e.g. a 10-license key can cover 5 instances in each product. AWS Marketplace deployments are metered per instance per hour through Amazon instead of DPA licenses. Trial allows 14 days of unlicensed monitoring.

DPA 2026.2 sizing brackets (per DPA server)

Monitored instancesDPA server (CPU · RAM · Disk)Repository DB (CPU · cache · Disk)
1 – 204 cores · 10 GB · 40 GB6 cores · 8 GB · 240 GB
21 – 506 cores · 16 GB · 55 GB8 cores · 16 GB · 600 GB
51 – 1008 cores · 24 GB · 75 GB12 cores · 32 GB · 1.2 TB
101 – 25012 cores · 40 GB · 150 GB16 cores · 64 GB · 3 TB

Above 250 instances, deploy additional DPA servers linked by DPA Central (0–50 users: 4 cores · 4 GB · 20 GB; 51–100 users: 6 cores · 6 GB · 20 GB, added to a monitoring server's spec). Registering VMware raises DPA server CPU & RAM by ~50%.

How this is calculated

  • DPA licenses are counted per monitored database instance (self-managed and Azure Marketplace). AWS Marketplace deployments are metered per instance per hour through Amazon and need no DPA licenses; licenses and metering cannot mix on one server.
  • DBSH covers any edition of any supported database type and includes VM metrics. DBSHDS covers DBaaS targets such as Azure SQL Database. Legacy Cat 1 / Cat 2 / Azure SQL DB / VM Option licenses apply to DPA 2024.3 and earlier only.
  • Licenses float — more instances can be registered than licensed, with licenses assigned on the allocation page. Unlicensed instances stop collecting new data but keep historical data viewable.
  • Server count = total instances ÷ 250 (rounded up); instances are split evenly across servers and each server is sized by its bracket (1–20 / 21–50 / 51–100 / 101–250) from the DPA 2026.2 system requirements. Recommended uses the next bracket up plus a dedicated repository server.
  • Multiple DPA servers are linked via DPA Central, co-located on a monitoring server (not a dedicated box), sized by concurrent users.
Sources
  • DPA licensing model — per-instance counting, DBSH/DBSHDS, legacy Cat 1/Cat 2, floating licenses, SQL Sentry shared keys, AWS metering.
  • DPA 2026.2 system requirements — DPA server & repository brackets, DPA Central recommendations, repository database support.

Indicative SE sizing estimate for SolarWinds DPA. License quantities, license types, and final hardware must be validated in CPQ and against the customer's live environment and current DPA system-requirements documentation before quoting.

\n