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.
Each measurement is obtained per ThousandEyes test interval.
For details about all ThousandEyes metric types, check ThousandEyes Knowledge Base | ThousandEyes Documentation and ThousandEyes End-to-End Metrics | ThousandEyes Documentation.
The following table is an overview of the ThousandEyes metric and corresponding Nobl9 values:
Metric | Nobl9 Value |
---|---|
Network Latency | net-latency |
Network loss | net-loss |
Page load | web-page-load |
DOM load time | web-dom-load |
HTTP Server Response | http-response-time |
HTTP Server Availability | http-server-availability |
HTTP Server Throughput | http-server-throughput |
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
.
Adding ThousandEyes as a Data Source in the UI
To add ThousandEyes as a data source in Nobl9 using the Agent or Direct connection method, follow these steps:
- Navigate to Integrations > Sources.
- Click the
button.
- Click the relevant Source icon.
- Choose a relevant connection method (Agent or Direct), then configure the source as described below.
ThousandEyes Direct
Direct Configuration in the UI
Direct configuration for ThousandEyes requires users to enter their credentials which Nobl9 stores safely. Follow these steps to set up a direct configuration:
- Enter your OAuth Bearer Token.
Refer to the Authentication section above for more details.
- Select a Project.
Specifying a Project is helpful when multiple users are spread across multiple teams or projects. When the Project field is left blank then object is assigned to projectdefault
. - Enter a Display Name.
You can enter a friendly name with spaces in this field. - Enter a Name.
The name is mandatory and can only contain lowercase, alphanumeric characters and dashes (for example,my-project-name
). This field is populated automatically when you enter a display name, but you can edit the result. - Enter a Description.
Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it. - Click the Add Data Source
ThousandEyes Agent
Agent Configuration in the UI
Follow the instructions below to configure your ThousandEyes Agent. Refer to the section above for the description of the fields.
- Enter a Project.
- Enter a Display Name.
- Enter a Name.
- Create a Description.
- Click the Add Data Source
Agent Using CLI - YAML
The YAML for setting up an Agent connection to ThousandEyes looks like this:
apiVersion: n9/v1alpha
kind: Agent
metadata:
name: thousandeyes
displayName: ThousandEyes # optional
project: thousandeyes
spec:
sourceOf:
- Metrics
- Services
thousandEyes: {}
You can deploy only one Agent in one YAML file by using the sloctl apply
command.
Deploying ThousandEyes Agent
When you add the data source, Nobl9 automatically generates a Kubernetes configuration and a Docker command line for you to use to deploy the Agent. Both of these are available in the web UI, under the Agent Configuration section. Be sure to swap in your credentials (e.g., replace <OAUTH_BEARER_TOKEN>
with your actual token).
- Kubernetes
- Docker
If you use Kubernetes, you can apply the supplied YAML config file to a Kubernetes cluster to deploy the Agent. It will look something like this:
# DISCLAIMER: This deployment description contains only the fields necessary for the purpose of this demo.
# It is not a ready-to-apply k8s deployment description, and the client_id and client_secret are only exemplary values.
apiVersion: v1
kind: Secret
metadata:
name: nobl9-agent-nobl9-dev-thousandeyes-secret
namespace: default
type: Opaque
stringData:
thousandeyes_oauth_bearer_token: "<THOUSANDEYES_OAUTH_BEARER_TOKEN>"
client_id: "unique_client_id"
client_secret: "unique_client_secret"
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: nobl9-agent-nobl9-dev-thousandeyes-agent-deployment
namespace: default
spec:
replicas: 1
selector:
matchLabels:
nobl9-agent-name: "my-unique-agent-name"
nobl9-agent-project: "thousandeyes"
nobl9-agent-organization: "nobl9-dev"
template:
metadata:
labels:
nobl9-agent-name: "my-unique-agent-name"
nobl9-agent-project: "thousandeyes"
nobl9-agent-organization: "nobl9-dev"
spec:
containers:
- name: agent-container
image: nobl9/agent:latest
resources:
requests:
memory: "350Mi"
cpu: "0.1"
env:
- name: N9_CLIENT_ID
valueFrom:
secretKeyRef:
key: client_id
name: nobl9-agent-nobl9-dev-thousandeyes-secret
- name: N9_CLIENT_SECRET
valueFrom:
secretKeyRef:
key: client_secret
name: nobl9-agent-nobl9-dev-thousandeyes-secret
- name: THOUSANDEYES_OAUTH_BEARER_TOKEN
valueFrom:
secretKeyRef:
key: thousandeyes_oauth_bearer_token
name: nobl9-agent-nobl9-dev-thousandeyes-secret
# The N9_METRICS_PORT is a variable specifying the port to which the /metrics and /health endpoints are exposed.
# The 9090 is the default value and can be changed.
# If you don’t want the metrics to be exposed, comment out or delete the N9_METRICS_PORT variable.
- name: N9_METRICS_PORT
value: "9090"
If you use Docker, you can run the Docker command to deploy the Agent. It will look something like this:
docker run -d --restart on-failure \
--name nobl9-agent-nobl9-dev-thousandeyes-agent \
-e N9_CLIENT_ID="unique_client_id" \
-e N9_CLIENT_SECRET="unique_client_secret" \
# The N9_METRICS_PORT is a variable specifying the port to which the /metrics and /health endpoints are exposed.
# The 9090 is the default value and can be changed.
# If you don’t want the metrics to be exposed, comment out or delete the N9_METRICS_PORT variable.
-e N9_METRICS_PORT=9090 \
-e THOUSANDEYES_OAUTH_BEARER_TOKEN="" \
nobl9/agent:latest
Creating SLOs with ThousandEyes
Creating SLOs in the UI
Follow the instructions below to create your SLOs with ThousandEyes in the UI:
Navigate to Service Level Objectives.
- Click the
button.
In step 1 of the SLO wizard, select the Service the SLO will be associated with.
In step 2, select ThousandEyes as the Data Source for your SLO, then specify the Metric. For ThousandEyes you can use only a Threshold Metric, where a single time series is evaluated against a threshold, The ThousandEyes metric specification has two fields:
testID
andtestType
.Enter a
testID
. It is an ID of the test configured in ThousandEyes. It is a mandatory field, and it must be a positive number.Choose a
testType
. It is a ThousandEyes metric. You can choose between the following ThousandEyes metrics supported by Nobl9 (refer to the Scope of Support section for more details):Network Latency
Network Loss
Page Load
DOM Load Time
HTTP Server Response
HTTP Server Availability
HTTP Server Throughput
In step 3, define a Time Window for the SLO.
In step 4, specify the Error Budget Calculation Method and your Objective(s).
In step 5, add a Name, Description, and other details about your SLO. You can also select Alert Policies and Labels on this screen.
When you’re done, click Create SLO.
SLO using ThousandEyes - YAML samples
- Web page load
- Response time
- Net latency
- DOM load
- Net loss
- Server Availability
- Server Throughput
- apiVersion: n9/v1alpha
kind: SLO
metadata:
name: my-thousandeyes-web-page-load-time-rolling-occurrences
project: thousandeyes
spec:
service: thousandeyes
indicator:
metricSource:
name: thousandeyes
timeWindows:
- unit: Hour
count: 1
isRolling: true
budgetingMethod: Occurrences
objectives:
- displayName: Good
op: lte
rawMetric:
query:
thousandEyes:
testID: 2280492
testType: web-page-load
value: 75
target: 0.90
- apiVersion: n9/v1alpha
kind: SLO
metadata:
name: my-thousandeyes-response-time-rolling-occurrences
project: thousandeyes
spec:
service: thousandeyes
indicator:
metricSource:
name: thousandeyes
timeWindows:
- unit: Hour
count: 1
isRolling: true
budgetingMethod: Occurrences
objectives:
- displayName: Good
op: lte
rawMetric:
query:
thousandEyes:
testID: 2014018
testType: http-response-time
value: 75
target: 0.90
- apiVersion: n9/v1alpha
kind: SLO
metadata:
name: my-thousandeyes-net-latency-calendar-occurrences
project: thousandeyes
spec:
service: thousandeyes
indicator:
metricSource:
name: thousandeyes
timeWindows:
- unit: Day
count: 1
calendar:
startTime: 2020-03-09 00:00:00
timeZone: Europe/Warsaw
budgetingMethod: Occurrences
objectives:
- displayName: Good
op: lte
rawMetric:
query:
thousandEyes:
testID: 2014018
testType: net-latency
value: 75
target: 0.90
- apiVersion: n9/v1alpha
kind: SLO
metadata:
name: my-thousandeyes-web-dom-load-rolling-timeslices
project: thousandeyes
spec:
service: thousandeyes
indicator:
metricSource:
name: thousandeyes
timeWindows:
- unit: Day
count: 7
isRolling: true
budgetingMethod: Timeslices
objectives:
- displayName: Good
op: lte
rawMetric:
query:
thousandEyes:
testID: 2280492
testType: web-dom-load
value: 40
target: 0.50
timeSliceTarget: 0.50
- displayName: Moderate
op: lte
rawMetric:
query:
thousandEyes:
testID: 2280492
testType: web-dom-load
value: 45
target: 0.75
timeSliceTarget: 0.75
- displayName: Annoying
op: lte
rawMetric:
query:
thousandEyes:
testID: 2280492
testType: web-dom-load```
value: 50
target: 0.95
timeSliceTarget: 0.95
- apiVersion: n9/v1alpha
kind: SLO
metadata:
name: my-thousandeyes-net-loss-rolling-timeslices
project: thousandeyes
spec:
service: thousandeyes
indicator:
metricSource:
name: thousandeyes
rawMetric:
thousandEyes:
testID: 2014018
testType: net-loss
timeWindows:
- unit: Day
count: 1
isRolling: true
budgetingMethod: Timeslices
objectives:
- displayName: Good
op: lte
value: 75
target: 0.90
timeSliceTarget: 0.9
apiVersion: n9/v1alpha
kind: SLO
metadata:
name: server-availability-rolling-occurrences
project: thousandeyes
spec:
service: thousandeyes
indicator:
metricSource:
name: thousandeyes
timeWindows:
- unit: Hour
count: 1
isRolling: true
budgetingMethod: Occurrences
objectives:
- displayName: Good
op: lte
rawMetric:
query:
thousandEyes:
testID: 2748593
testType: http-server-availability
value: 300
target: 0.90
apiVersion: n9/v1alpha
kind: SLO
metadata:
name: server-throughput-calendar-timeslices
project: thousandeyes
spec:
service: thousandeyes
indicator:
metricSource:
name: thousandeyes
timeWindows:
- unit: Day
count: 7
calendar:
startTime: 2020-03-09 00:00:00
timeZone: Europe/Warsaw
budgetingMethod: Timeslices
objectives:
- displayName: Good
op: lte
rawMetric:
query:
thousandEyes:
testID: 2123016
testType: http-server-throughput
value: 3000000
target: 0.90
timeSliceTarget: 0.90
Important notes:
The ThousandEyes metric specification expects two fields: testID
and testType
.
testID
is an ID of the test configured in ThousandEyes. It is a mandatory field, and it must be a positive number.testType
is an end-to-end ThousandEyes metric. It is a string field. Enter one of the below ThousandEyes metrics supported by Nobl9 (for more details, refer to the Scope of Support section above).net-latency
net-loss
web-page-load
web-dom-load
http-response-time
http-server-availability
http-server-throughput
When the testType
field is missing in the ThousandEyes YAML configuration, net-latency
value is assumed.
If you want to apply http-server-availability
and http-server-throughput
as testType
, update your Agent to the 0.52.0 version.
Querying the ThousandEyes Server
Nobl9 queries the ThousandEyes instance once every minute. If the Agent doesn’t collect any data in a given minute, the next query will be extended to the past two minutes.
ThousandEyes API Rate Limits
The ThousandEyes API throttles API requests using a 240 request-per-minute (per organization) limit with each page having max 1000 elements included.
Useful Links
Test Data | ThousandEyes Documentation
ThousandEyes Knowledge Base | ThousandEyes Documentation
ThousandEyes End-to-End Metrics | ThousandEyes Documentation
Agent Metrics | Nobl9 Documentation
Creating SLOs via Terraform | Nobl9 Terraform Documentation
Creating Agents via Terraform | Nobl9 Terraform Documentation