SolarWinds · Solutions Engineering · APJ
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)
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
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.
Contact us
Licensing
Licensable quantities for active modules only. Confirm all quantities in CPQ.
| Module | Unit of measure | Quantity |
|---|
Customer-side sizing
Documented minimum collector spec
| Component | Qty | CPU | RAM | Storage |
|---|
Recommended spec + HA / redundancy
| Component | Qty | CPU | RAM | Storage |
|---|
Reference
| Module | Entity / unit | Counts as |
|---|---|---|
| Network | Network device (router/switch/firewall) | 1:1 |
| Network | Wireless access point | 10:1 |
| Infrastructure | Host / server (agent or collector) | 1:1 |
| Infrastructure | Hypervisor / virtual host | 1:1 |
| Infrastructure | Standalone VM | 3:1 |
| Infrastructure | Cloud service (AWS/Azure, non-host) | 3:1 |
| Infrastructure | Kubernetes container | 10:1 |
| Infrastructure | Storage array | 1:1 |
| Infrastructure | ICMP-only status node | Free |
| APM | Application service (any # instances) | Per service |
| Database | Database instance | Per instance |
| DEM — Synthetic Uptime | Uptime check = endpoint × location × protocol | 10 uptime checks / bundle |
| DEM — Synthetic Transactions | Scripted transaction (5 checks each) | 2 transactions / bundle |
| DEM — RUM | Pageviews | Per 100,000 / month |
| Logs | Log ingestion | Per GB (monthly plan) |
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
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.
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.
Contact us
Reference
Selected tier highlighted. Advanced includes everything in Essentials plus the additional capabilities below.
| Capability | Essentials | Advanced |
|---|
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.
Reference
Matching tier highlighted. Standard up to 1,500 nodes; Enterprise from 500 and required beyond 1,500.
| Edition | Available node tiers |
|---|---|
| Standard | |
| Enterprise |
Hardware sizing
| Component | Qty | CPU | RAM | Storage |
|---|
| Component | Qty | CPU | RAM | Storage |
|---|
Reference
| Dimension | Per polling engine | Per instance |
|---|---|---|
| Elements — SNMPv2 | 100,000 (16 cores; +7,500/core → max 150,000) | 1,000,000 elements · 100 APEs |
| Elements — SNMPv3 | 72,000 (16 cores; +5,000/core → max 100,000) | |
| Elements — WMI/WinRM | 20,000 (max 2,000 nodes; +2,000/core → 30,000) | |
| SAM component monitors | 40,000 (APE) · ~10,000 (main) | 550,000 |
| NetFlow (NTA) — Advanced | 50,000 flows/sec | 300,000 flows/sec |
| SolarWinds agents | 1,000 (−10 per remote collector) | — |
| UDT ports | 100,000 | 500,000 |
| VMAN VMs — Advanced | 10,000 (per APE) | — |
| Web console users | 25–50 per web server | 50–100 (main) |
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
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
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.
Contact us
Reference
Matching tier highlighted. Standard up to 1,500 nodes; Enterprise from 500 and required beyond 1,500.
| Edition | Available node tiers |
|---|---|
| Standard | |
| Enterprise |
Hardware sizing
| Component | Qty | CPU | RAM | Storage |
|---|
| Component | Qty | CPU | RAM | Storage |
|---|
| Component | Qty | CPU | RAM | Storage |
|---|
| Component | Qty | CPU | RAM | Storage |
|---|
Reference
| Dimension | Per polling engine | Per instance |
|---|---|---|
| Elements — SNMPv2 | 100,000 (16 cores; +7,500/core → max 150,000) | 1,000,000 elements · 100 APEs |
| Elements — SNMPv3 | 72,000 (16 cores; +5,000/core → max 100,000) | |
| Elements — WMI/WinRM | 20,000 (max 2,000 nodes; +2,000/core → 30,000) | |
| SAM component monitors | 40,000 (APE) · ~10,000 (main) | 550,000 |
| NetFlow (NTA) | 50,000 flows/sec | 300,000 flows/sec |
| SolarWinds agents | 1,000 (−10 per remote collector) | — |
| SRM LUNs | 40,000 | 160,000 |
| UDT ports | 100,000 | 500,000 |
| VMAN VMs | 10,000 (per APE) | — |
| Web console users | 25–50 per web server | 50–100 (main) |
| SaaS Network Collector | 7,000 standard devices · 40,000 flows/sec | deploy multiple |
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
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
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.
Contact us
Licensing
Licensable quantities for the current scope. Confirm all quantities in CPQ.
| License | Unit of measure | Quantity |
|---|
Hardware sizing
| Component | Qty | CPU | RAM | Storage |
|---|
| Component | Qty | CPU | RAM | Storage |
|---|
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.
Reference
| License | Status | Coverage |
|---|---|---|
| DBSH — Database Self-Hosted | Current subscription | Any 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 DBaaS | Current subscription | Supported DBaaS targets, such as Azure SQL Database. |
| Category 1 / Category 2 | Legacy (≤ 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 Database | Legacy (≤ DPA 2024.3) | Azure SQL Database instances. |
| VM Option | Legacy (≤ 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.
Reference
| Monitored instances | DPA server (CPU · RAM · Disk) | Repository DB (CPU · cache · Disk) |
|---|---|---|
| 1 – 20 | 4 cores · 10 GB · 40 GB | 6 cores · 8 GB · 240 GB |
| 21 – 50 | 6 cores · 16 GB · 55 GB | 8 cores · 16 GB · 600 GB |
| 51 – 100 | 8 cores · 24 GB · 75 GB | 12 cores · 32 GB · 1.2 TB |
| 101 – 250 | 12 cores · 40 GB · 150 GB | 16 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%.
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.