SolarWinds Observability Pricing
SolarWinds Observability is designed to provide customers with maximum flexibility and choice. It’s a unified platform offering modules with discrete capabilities so you can scale seamlessly as your needs grow.
Starts at:
Per application instance*
Real-time application metrics, distributed tracing, & code profiling
Starts at:
Per active network device or host*
Network devices and hosts (1:1), cloud services (3:1), containers (10:1)
Starts at:
Per database instance*
Deep database performance analysis with root cause diagnostics
Starts at:
Per 10 uptime checks*
Synthetic Monitoring - Availability and performance insights
Starts at:
Per 100,000 page views*
Real user monitoring – gain insights into how actual users experience your websites
*USD per month, billed annually
SWO Pricing FAQ
It is the number of service instances to be instrumented for monitoring. Application Observability has a one-to-one relationship with the number of service instances you need to monitor. Order five (5) service instances if you have an application consisting of five service instances you want to instrument to collect metrics, traces, code profiles, and more.
You can choose the number of network devices, the number of hosts, or any combination of both. The number of network devices or hosts is based on the maximum active number within the previous calendar day. Active means SolarWinds® Observability received telemetry data from the host or the network device in the previous 24-hour window.
Network devices and hosts are defined as follows:
- Any network device, router, hub, etc. (1:1 ratio)
- Any host with a SolarWinds host agent installed (1:1 ratio)
- Any non-host cloud service (AWS, Azure; 3:1 ratio)
- If using containers, they will have a 10:1 ratio with hosts)
Example: If I have 20 network devices, 10 file servers, 100 containers (100/10) running my applications, and 12 Amazon cloud services (12/3), I’ll order a quantity of 44 of the Network and Infrastructure Observability SKUs.
It is the amount of logs ingested in a calendar month in GB.
Log Observability plans are designed to be simple and are sold in increments of 1GB/month. If you want to ingest 100GB in a month, you need to purchase a quantity of 100. You can choose between monthly and annual plans with retention periods from one to 60 days (If you prefer longer retention, please get in touch with sales). You can start, upgrade, or downgrade logging plans during the month, and plan changes are prorated.
Overage will be allowed by default. At the end of a calendar month, SolarWinds will add up the sum of usage for that month, and the portion above the monthly plan will be considered as overage.
The Database Observability entitlement will be based on a daily high watermark of active database instances. Active database instance means it has received telemetry data (metrics, logs, etc.) in the previous calendar day. Furthermore, a database instance is defined as having a Database Observability agent installed. AWS RDS that we inferred from the CloudWatch metric would not be counted as a database instance, unless it was being monitored by a DBO agent.
The number of uptime check bundles, with ten checks per bundle.
First determine how many checks you want to configure for each website in your organization. Then add all checks for each website to find a total number of checks for your organization.
Use the following formula to determine how many checks are configured for each website: Tested protocols X Locations tested from = Checks configured.
If you want to test a website’s availability and response time from London and Los Angeles using both the HTTPS and HTTP protocols, you will need four (4) uptime checks for that website.
If you have ten (10) websites you want to monitor with that same configuration, the total number of uptime checks for your organization would be 40.
Each Digital Experience Monitoring – Synthetics availability bundle comes with ten (10) uptime checks. To observe these websites, order a quantity of four Digital Experience Monitoring – Synthetics bundles.
For each uptime check you purchase, you can run its individual tests as frequently as every 60 seconds. You will only pay per check configured, no matter how frequently the check’s tests run. For the example above, with 40 tests configured you could run up to 57,600 tests a day, every day.
Real User Monitoring (RUM) is charged in blocks of 100,000 page views. To decide how many blocks to order for the website/websites you want to gain insights into, simply take the total number of page views needed and divide by 100,000. For example, if you need 1,200,000 page views, you will need to order a quantity of 12 of this SKU. 1,200,000/100,000 = 12.