ThousandEyes
ThousandEyes monitors the performance of both local and wide-area networks. ThousandEyes combines Internet and WAN visibility, browser synthetics, end-user monitoring, and Internet Insights to deliver a holistic view of your hybrid digital ecosystem β across cloud, SaaS, and the Internet. It's a SaaS-based tool that helps troubleshoot application delivery and maps Internet performance.
Scope of supportβ
Currently, Nobl9 integration with ThousandEyes supports the following metrics:
-
Network Latency - is the interval time (in milliseconds) from sending a network packet to when the test-assigned agent receives the response.
-
Network Loss - is the total loss of the network packet (in percents).
-
Page Load - is the interval of time (in milliseconds) from the load event to the point when the website is loaded.
-
DOM Load Time - is the interval of time (in milliseconds) required for the browser to build the websiteβs Document Object Model (DOM)
-
HTTP Server Response - is the interval between the beginning of the request and the web server successfully sending the first byte of the response to the client.
-
HTTP Server Availability - is the availability for a given agent. For HTTP Server Availability, Nobl9 receives status codes of an
http
response, for example, 200, 201, 400, or 501.warningWhen there are multiple ThousandEyes agents, Nobl9 can receive multiple HTTP response status codes in a single request. In this situation, Nobl9 ingests only the highest status code.
-
HTTP Server Throughput - is the Wire Size divided by the Receive Time (in bits per second). For more information, refer to the ThousandEyes documentation.
-
HTTP Server Total Time - time (in milliseconds) of ThousandEyes agent receiving the last byte of your server's response.
-
DNS Server Resolution Time - time (in milliseconds) of ThousandEyes agent receiving the response from the DNS server about your domain.
-
DNS DNSSEC Valid - 1 if keychain for a domain record is valid, 0 otherwise.
Each measurement is obtained per ThousandEyes test interval.
For details about all ThousandEyes metric types, check ThousandEyes Knowledge Base | ThousandEyes documentation and ThousandEyes Test Data | ThousandEyes documentation.
The following table is an overview of the supported ThousandEyes tests and corresponding Nobl9 names:
Name | Response property read | Nobl9 YAML name | Aggregation* | Minimum agent (supported channel) |
---|---|---|---|---|
Network > End-to-End metrics | avgLatency | net-latency | mean | 0.33.0 (stable, beta) |
Network > End-to-End metrics | Loss | net-loss | mean | 0.33.0 (stable, beta) |
Web > Page load | pageLoadTime | web-page-load | mean | 0.33.0 (stable, beta) |
Web > Page load | domLoadTime | web-dom-load | mean | 0.33.0 (stable, beta) |
Web > HTTP server | responseTime | http-response-time | mean | 0.33.0 (stable, beta) |
Web > HTTP server | responseCode | http-server-availability | max | 0.52.0 (stable, beta) |
Web > HTTP server | throughput | http-server-throughput | mean | 0.52.0 (stable, beta) |
Web > HTTP server | totalTime | http-server-total-time | mean | 0.68.0-beta01 (beta) 0.67.2 (stable) |
DNS > Server metric | resolutionTime | dns-server-resolution-time | mean | 0.68.0-beta01 (beta) 0.67.2 (stable) |
DNS > DNSSEC | valid | dns-dnssec-valid | logical conjunction | 0.68.0-beta01 (beta) 0.67.2 (stable) |
*) If your test returns more than one result per round.
Whenever your ThousandEyes SLO has incompatible data source version/channel, the SLO config won't be served to your data source.
Authenticationβ
Nobl9 requires OAUTH_BEARER_TOKEN
to communicate with ThousandEyes.
To get the OAUTH_BEARER_TOKEN
:
-
Log in to your ThousandEyes account.
-
Navigate to Account Settings.
-
Select Users and Roles.
-
Navigate to the bottom of the page and you will see User API Tokens.
-
Select OAuth Bearer Token.
Currently, Nobl9 only supportsOAUTH_BEARER_TOKEN
.