Integrations
ThousandEyes integrations enable seamless integration of ThousandEyes metrics, alerts, and test data into your existing workflows for monitoring, incident response, and automation. You can route alerts to tools like PagerDuty or Slack for real-time triage within your on-call processes, use test recommendations to optimize monitoring for critical services, or export telemetry via OpenTelemetry or APIs to platforms like AppDynamics for unified dashboards. Custom webhooks allow tailored automation, such as updating tickets or triggering scripts. Continuously updated integration options provide flexibility to adapt to your operational needs.
Integration Methods
ThousandEyes is transitioning to a new integration experience that separates connection settings from operational logic. Integrations are available in either the original format (v1) or the new format (v2), depending on the specific integration. There’s no manual choice between versions—each integration is only available in one format. Once an integration is migrated to v2, it is no longer available in v1.
The v2 experience introduces reusable connectors, which allow you to configure a single connection to a third-party service and associate it with multiple operations. This improves scalability, simplifies management, and reduces duplication across your integrations.
In contrast, v1 integrations combine connection details and operation settings in a single configuration. This requires you to create and manage a separate integration for each use case, even if they connect to the same service.
Version 1 (Classic)
In v1 integrations, you configure both the connection to the third-party service and the specific interaction logic in a single setup. If you need to perform multiple operations with the same service, you must create a new integration for each one.
Version 2
In v2 integrations, you create a connector to establish the connection between ThousandEyes and the third-party service. Once the connector is in place, you can define and manage multiple operations that reuse the same connector. This modular design streamlines configuration, reduces redundancy, and supports better scaling as your integration needs grow. For step-by-step instructions, see Creating a New Integration.
ThousandEyes for OpenTelemetry integrations can also be configured using the API. For more information, see ThousandEyes for OpenTelemetry API.
Note that while a connector can support multiple operations, operations are limited to a single connector.
The following integrations are available for version 2:
Creating a New Integration
Creating an Integration Using Templates
Integration templates streamline the connector and operation creation process. Use templates to create a connector and operation in one step. For a list of available templates, in the ThousandEyes app, navigate to Manage > Integrations. Click the Integrations 2.0 tab. Click on the Integrations Templates tab.

Templates are available for the following integrations:
Choosing a Connector for a Third-party Service
Connectors establish secure communication between ThousandEyes and third-party applications. Most integrations use REST APIs or gRPC token exchanges to enable read access to specific data sets. These widely compatible, straightforward integrations are referred to as generic connectors.

To create the link:
Specify the domain you want ThousandEyes to retrieve data from
Specify an authentication type
Provide the key or token

Generic connectors can include preset fields, which can simplify setup, ensure consistency, and reduce the risk of configuration errors. Access preset fields from the Preset Configurations dropdown. Select from the listed templates to automatically populate configuration fields with recommended values.
Creating Operations for a New Connector
After you create a connector, you will be prompted to choose or create an operation to connect it to.
With operations, you can define how to use and configure the data that gets exchanged between the third-party service and ThousandEyes. Operation types define what you can do with the third-party service's data.
From the UI, choose a type to customize the operation:

Enable or disable ThousandEyes interacting with your third-party app. This can be useful, for example, to disable alert notifications being sent to the third-party app, or to temporarily decrease costs on an integration with third-party cost implications, such as AWS data transfer fees.
Operation screen showing Enable toggle If the operation requires further third party-specific information, you can add it here. For example, when sending alert notifications, you can specify the Slack channel they should go to, or the AppDynamics Node and Tier.
Additional Slack-specific fields Add further ThousandEyes-specific information here. For example, when streaming test data to OpenTelemetry, you can specify the tests you want to nominate. You can also specify the template for the webhook headers, query parameters, and body when sending a custom webhook alert notification.
Additional ThousandEyes-specific fields

Once both connector and operation are configured, navigate to the Operations screen to show the status of the integration. If successful, the integration shows a status of Connected
on the Operation screen. Some connections may require further steps to resolve a status of Pending
to Connected
.


Managing an Existing Operation
To view a list of existing operations:
Navigate to Manage > Integrations. Select Integrations 2.0.
Click on the Operations tab.
A list of operations appears with the following sortable columns: Last Modified, Operation Name, Enabled, Status, Type, and Connector Name.

To edit an existing operation:
From the list of existing operations, find the operation you want to edit and select the row.
In the side modal that appears, update any fields you want to change.
Click the Save button to save the operation. If you haven't assigned it to a connector and you would like to, click Save and Assign Connector.
To delete an existing operation:
From the list of existing operations, find the operation you want to delete and select the vertical three dots at the end of its row.
Select
Delete
from the drop-down that appears.
Managing an Existing Connector
To view a list of existing connectors:
Navigate to Manage > Integrations. Select Integrations 2.0.
Click on the Connectors tab.
A list of connectors appears with the following sortable columns: Last Modified, Connector Name, Type, URL, Assigned Operations.

To edit an existing connector:
From the list of existing connectors, find the connector you want to edit and select the vertical three dots at the end of its row.
Select
Edit
from the drop-down that appears.In the side modal that appears, update any fields you want to change.
Click the Save button to save the connector. If you haven't assigned it to an operation and you would like to, click Save and Assign Operation.
To view a list of operations associated with a connector:
From the list of existing connectors, find the connector you want to view operations for and select the vertical three dots at the end of its row.
Select
Manage Operations
from the drop-down that appears.In the side modal, a list of operations appears.
Adding an Operation to an Existing Connector
Navigate to Manage > Integrations. Select Integrations 2.0.
Click on the Connectors tab.
From the list of connectors, find the connector you want to associate with the operation and select the vertical three dots at the end of its row.
Select
Manage Operations
from the drop-down that appears.In the side modal, a list of operations appear.
Click
+ New Operation
at the top of the side modal.Follow the instructions to configure the new operation. See the section Creating Operations For a New Connector.
Last updated