ThousandEyes for OpenTelemetry

OpenTelemetry (OTel) is an open-source project that provides a vendor-neutral, standardized way to instrument, generate, collect, and export telemetry data for cloud-native applications. It helps developers easily incorporate observability into their services, enabling better monitoring, debugging, and optimization of their applications.
ThousandEyes for OpenTelemetry provides machine-to-machine integration between ThousandEyes and its customers. It allows you to export ThousandEyes telemetry data in OTel format, which is widely used in the industry. With ThousandEyes for OTel, you can leverage frameworks widely used in the observability domain - such as Splunk, Grafana, and Honeycomb - to capture and analyze ThousandEyes data. Any client that supports OTel can use ThousandEyes for OpenTelemetry.
ThousandEyes for OTel is made up of the following components:
  • Data streaming APIs that you can use to configure and enable your ThousandEyes tests with OTel-compatible streams, in particular to configure how ThousandEyes telemetry data is exported to client integrations.
  • A set of streaming pipelines called collectors that actively fetch ThousandEyes network test data, enrich the data with some additional detail, filter, and push the data to the customer-configured endpoints, depending on you configure via the public APIs.
  • Third-party OTel collectors that receive, transform, filter, and export different metrics to client applications such as AppD, or any other OTel-capable client configuration.


  • Limits: 1 stream and 250 tests per account group.
  • The following test types are currently supported:
    • Agent-to-server
    • Agent-to-agent
    • HTTP server
    • Web transaction
    • Page load (network layer only)
    • FTP server (network layer only)
    • DNS server (network layer only)
    • SIP server (network layer only)
  • ThousandEyes for OpenTelemetry currently supports the following test metrics:
    • Network - latency, loss, and jitter.
    • Web HTTP server layer - availability, response time, and throughput.
    • Web transactions - page load time, transaction time, completion, and errors.