How Unit Consumption Works
ThousandEyes bills for scheduled tests and instant tests based on whether the test is run from a Cloud Agent or an Enterprise Agent, and for two-way tests (agent-to-agent tests) whether the target agent is a Cloud Agent or an Enterprise Agent. Any test run from or to a Cloud Agent will incur a cost in units. When a test is run, the test's cost is deducted from the monthly units purchased by the customer's organization, as specified in the customer's contract. Each month the account is reset to the number of units that was contracted by the customer's organization.

Calculating the Cost of a Test

For tests that incur units, the cost in units is based on the following:
  1. 1.
    Type of test
  2. 2.
    Test interval setting (frequency)
  3. 3.
    Number of ThousandEyes Agents running the test
  4. 4.
    Test Timeout setting
These settings are available for each test from the Test Settings page, on the Basic Configuration tab (1 - 3) and the Advanced Settings tab (4):
The number of units that a test consumes per hour is calculated according to the following formula:
The test interval parameter is measured in minutes. The number of units per test run is listed in the following table.
Test Type
Units Per Test Run
Notes
Agent-to-server
0.005 or 0.0025
Cloud Agent or Enterprise Agent (source)
Agent-to-agent
0.005 or 0.0025
Cloud Agent or Enterprise Agent (source), per direction
DNS server
0.005 or 0.0025 per DNS server
Cloud Agent or Enterprise Agent (source)
DNS trace and DNSSEC
0.005 or 0.0025
Cloud Agent or Enterprise Agent (source)
HTTP server
0.001 or 0.0005 x Timeout setting (in seconds)
Cloud Agent or Enterprise Agent (source)
FTP server
0.001 or 0.0005 x Timeout setting (in seconds)
Cloud Agent or Enterprise Agent (source)
Page load
0.001 or 0.0005 x Timeout setting (in seconds)
Cloud Agent or Enterprise Agent (source)HTTP Server; see note below
Web transaction
0.001 or 0.0005 x Timeout setting (in seconds)
Cloud Agent or Enterprise Agent (source) Minimum Timeout is 5 seconds, maximum is 180 seconds
BGP
8
The cost of a Routing Layer BGP test is independent of the number of BGP monitors selected
Voice - SIP server
0.001 or 0.0005 x Timeout setting (in seconds)
Cloud Agent or Enterprise Agent (source)
Voice - RTP stream
0.001 or 0.0005 x Timeout setting (in seconds)
Cloud Agent or Enterprise Agent (source)
Note Regarding Page Load Tests
Page load tests allow the configuration of different frequencies for the Page Load view and HTTP Server view. If the timeouts are different, the consumption of units is calculated using the frequencies of both views. Consider the following example:
One page load test running from one Cloud Agent, with a frequency of 15 minutes, with a 30-second timeout. The hourly consumption for this test would be 0.12 units:
1
1 Cloud Agent x 0.03 units per run x (60 minutes per hour / 15 minutes) = 0.12 units per hour.
Copied!
When the testing interval for HTTP server tests is reduced from 15 minutes to 5 minutes, we are now running 12 HTTP server tests for the HTTP Server view. The calculation is thus 4 page load tests and 12 - 4 = 8 additional HTTP server tests. Assuming a 5-second HTTP server timeout setting, this causes the hourly consumption to increase to 0.16 units per hour:
1
1 Cloud Agent x 0.03 units per run x (60 minutes per hour / 15 minutes) = 0.12 units per hour. (Page Load)
2
1 Cloud Agent x 0.005 units per run x ( (60/5) - (60/15) ) = 0.04 units per hour (additional HTTP Server tests)
Copied!
0.12 + 0.04 = 0.16 units per hour

Why This Model?

We’ve chosen this model to allow our customers to have flexibility in test deployment. Rather than locking in a contract based on specific test types, locations and intervals, we’ve given you enough flexibility to manage your own testing use cases. Consider the following Cloud Agent scenario: Acme Manufacturing has purchased a total of 10 page load tests running at 15 minute interval from 20 locations, for a total monthly consumption of 17,856 units.
Test Type
Cloud Agent Locations
Tests
Interval (mins)
Timeout
Monthly unit consumption
Page load
20
10
15
30s/5s
17,856
Acme subsequently purchases another company, and needs to monitor a new website, as well as an API integration website for their product, meaning addition of 1 HTTP server test every 5 minutes from as many locations as possible, one page load test for the new company’s website, and one DNS trace test to validate the new company’s DNS configuration. Rather than extending the contract, they are able to be flexible in the deployment of the new tests by reducing the number of agents running the page load test from 20 to 16, and reallocating the saved units to the new tests:
Test Type
Cloud Agent Locations
Tests
Interval (mins)
Timeout
Monthly unit consumption
Page load
16
11
15
30s/5s
15,713
DNS trace
20
1
5
5s
892
Basic HTTP
20
1
5
5s
892
Total
17,498
This would leave 357 units available for additional tests.

Frequently Asked Questions

How are units deducted from my balance?

Every time a test is run, the number of units consumed by the test are deducted from the balance on the organization’s account. This information is accessible to users having a role with the View organization usage permission, by navigating in the app to Account Settings > Usage tab.

How can I estimate the consumption of units by a test?

ThousandEyes provides a calculator for customers to determine the cost of a test based on the inputs:

How can I view my balance?

Users who have a role that includes the View organization usage permission can view both to-date usage and usage projected to the end of the billing period. To do so, go to the Account Settings > Usage tab. For organizations that have multiple accounts, administrators can view a breakdown on an account-by-account basis.

What is the projected usage?

Projected usage is calculated by taking the current amount of units consumed and adding to it the current rate of unit consumption X the remain days in the billing cycle. This projection changes if test configurations change with alter the rate of unit consumption.

What happens if my organization exceeds our monthly quota of units?

The billing contact for the organization will be notified by email when any of the following are true:
  • When projected usage for the month reaches 100%, we will not allow you to set up new scheduled tests.
  • If actual usage for the month still reaches 100% (i.e. through the use of a large number of instant tests), we will disable scheduled tests to stop unit consumption.
  • We will not bill for overages.
For more information on alerting based on unit consumption, see Alerting for Test Unit Consumption.
Last modified 1mo ago