ThousandEyes

Reading time: 0 minute(s) (0 words)

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.

Authentication

Nobl9 requires OAUTH_BEARER_TOKEN to communicate with ThousandEyes.

To get the OAUTH_BEARER_TOKEN:

1. Log in to your ThousandEyes account.

2. Navigate to Account Settings.

3. Select Users and Roles.

4. Navigate to the bottom of the page and you will see User API Tokens.

5. Select OAuth Bearer Token.
   Currently, Nobl9 only supports OAUTH_BEARER_TOKEN.

Adding ThousandEyes as a data source

To ensure data transmission between Nobl9 and ThousandEyes, it may be necessary to list Nobl9 IP addresses as trusted.

💻ip allowlist

IP addresses to include in your allowlist for secure access:

If you're using app.nobl9.com instance:

• 18.159.114.21
• 18.158.132.186
• 3.64.154.26

If you're using us1.nobl9.com instance:

• 34.121.54.120
• 34.123.193.191
• 34.134.71.10
• 35.192.105.150
• 35.225.248.37
• 35.226.78.175
• 104.198.44.161

You can add the Thousandeyes data source using the direct or agent connection methods.

Direct connection method

Direct configuration for ThousandEyes requires users to enter their credentials which Nobl9 stores safely.

Nobl9 Web

Follow these steps to set up a direct configuration:

1. Navigate to Integrations > Sources.
2. Click .
3. Click the required Source button.
4. Choose Direct.

5. Select one of the following Release Channels:

   • The stable channel is fully tested by the Nobl9 team. It represents the final product; however, this channel does not contain all the new features of a beta release. Use it to avoid crashes and other limitations.
   • The beta channel is under active development. Here, you can check out new features and improvements without the risk of affecting any viable SLOs. Remember that features in this channel can change.

6. Enter your OAuth Bearer Token.
   Refer to the Authentication section above for more details.

7. 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, Nobl9 uses the default project.
8. Enter a Display Name.
   You can enter a user-friendly name with spaces in this field.
9. Enter a Name.
   The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
10. Enter a Description.
    Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
11. Specify the Query delay to set a customized delay for queries when pulling the data from the data source.

    • The default value in ThousandEyes integration for Query delay is 1 minute.

    info

    Changing the Query delay may affect your SLI data. For more details, check the Query delay documentation.
12. Click Add Data Source.

sloctl

1. Create a YAML definition to set up a direct connection with ThousandEyes. For this, refer to the following example:

YAML definition for the direct connection method

apiVersion: n9/v1alpha
kind: Direct
metadata:
  name: thousand-eyes
  displayName: ThousandEyes Direct
  project: default
spec:
  description: Example ThousandEyes Direct
  releaseChannel: stable
  thousandEyes:
    oauthBearerToken: "[secret]"
  queryDelay:
    value: 2
    unit: Minute

Field	Type	Description
queryDelay.unit mandatory	enum	Specifies the unit for the query delay. Possible values: Second | Minute. • Check query delay documentation for default unit of query delay for each source.
queryDelay.value mandatory	numeric	Specifies the value for the query delay. • Must be a number less than 1440 minutes (24 hours). • Check query delay documentation for default unit of query delay for each source.
logCollectionEnabled optional	boolean	Optional. Defaults to false. Set to true if you'd like your direct to collect event logs. Contact us to activate it.
releaseChannel mandatory	enum	Specifies the release channel. Accepted values: beta | stable.
Source-specific fields
thousandEyes.oauthBearerToken mandatory	string, secret	Required to communicate with ThousandEyes. See authentication section above for more details.

2. Apply your YAML definition using the sloctl apply command.

Agent connection method

Nobl9 Web

Follow the instructions below to configure your ThousandEyes agent.

1. Navigate to Integrations > Sources.
2. Click .
3. Click the required Source button.
4. Choose Agent.

5. Select one of the following Release Channels:

   • The stable channel is fully tested by the Nobl9 team. It represents the final product; however, this channel does not contain all the new features of a beta release. Use it to avoid crashes and other limitations.
   • The beta channel is under active development. Here, you can check out new features and improvements without the risk of affecting any viable SLOs. Remember that features in this channel can change.

6. 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, Nobl9 uses the default project.
7. Enter a Display Name.
   You can enter a user-friendly name with spaces in this field.
8. Enter a Name.
   The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
9. Enter a Description.
   Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
10. Specify the Query delay to set a customized delay for queries when pulling the data from the data source.

    • The default value in ThousandEyes integration for Query delay is 1 minute.

    info

    Changing the Query delay may affect your SLI data. For more details, check the Query delay documentation.
11. Click Add Data Source.
Deploy your agent in a Kubernetes cluster or Docker container.

sloctl

1. Create a YAML definition to set up an agent connection with ThousandEyes. For this, refer to the following example:

YAML definition for the agent connection method

apiVersion: n9/v1alpha
kind: Agent
metadata:
  name: thousand-eyes
  displayName: ThousandEyes Agent
  project: default
spec:
  description: Example ThousandEyes Agent
  releaseChannel: stable
  thousandEyes: {}
  queryDelay:
    value: 2
    unit: Minute

Field	Type	Description
queryDelay.unit mandatory	enum	Specifies the unit for the query delay. Possible values: Second | Minute. • Check query delay documentation for default unit of query delay for each source.
queryDelay.value mandatory	numeric	Specifies the value for the query delay. • Must be a number less than 1440 minutes (24 hours). • Check query delay documentation for default unit of query delay for each source.
releaseChannel mandatory	enum	Specifies the release channel. Accepted values: beta | stable.

1. Apply your YAML definition using the sloctl apply command.
2. Deploy your agent in a Kubernetes cluster or Docker container.

Useful links

For a more in-depth look, consult additional resources:

Test dataExternal docsThousandEyes knowledge baseExternal docsThousandEyes end-to-end metricsExternal docsAgent metricsAgentCreating SLOs via TerraformTerraformCreating agents via TerraformTerraform