Support and Limitations

Support

ThousandEyes for OpenTelemetry currently supports the following test types and OpenTelemetry signals and metrics:

Test Type

Metrics

Signals

Agent-to-server

Latency, loss, jitter

metrics

Agent-to-agent

Latency, loss, jitter

metrics

BGP

Path changes, reachability, updates

metrics

HTTP server

Availability, response time, throughput

metrics

Web transaction

Page load time, transaction time, completion, errors

metrics, traces

Page load

Page load time, completion

metrics, traces

FTP server

Availability, response time, throughput

metrics

DNS server

Availability, resolution time

metrics

DNS Domain Trace

Availability, final query time

metrics

DNS DNSSEC Trace

Validity

metrics

RTP stream

MOS, loss, discards, latency

metrics

SIP server

Availability, response time, total time

metrics

Endpoint Agent network

Loss, latency, jitter

metrics

Endpoint Agent HTTP

Availability, response time, throughput

metrics

API

Time, completion

metrics

For more information about the supported test types, metrics and attributes, see ThousandEyes for OpenTelemetry Metrics.

BGP metrics are event-driven, which means that they are streamed only when there is an announcement or withdrawal of a prefix by a monitor.

Test Layers

ThousandEyes tests are composed of multiple layers (see Test Type Layers and Units for more details). When creating a test, multiple test types may be applied, depending on the configuration. For example, an HTTP server test includes metrics from the Web, Network (agent-to-server test), and BGP layers by default.

ThousandEyes for OpenTelemetry captures and sends metrics from all enabled test layers. Below is an example breakdown of the metrics for an HTTP server test:

  • Web layer: Availability, Response Time, Throughput

  • Network layer: Latency, Packet Loss, Jitter

  • BGP layer: Path Changes, Reachability, Updates

Layer Configuration

You can customize which layers are active for different test types by modifying the API request body. For instance:

  • To disable the BGP layer, set "bgpMeasurements" to false in the REST API request body.

  • To disable the Network layer, set "networkMeasurements" to false in the REST API request body.

Example Test Types and Layer Configuration

  • agent-to-server - Create Agent to Server test

    • Disable BGP layer: "bgpMeasurements": false

  • agent-to-agent - Create Agent to Agent test

    • Disable BGP layer: "bgpMeasurements": false

  • dns-server - Create DNS Server test

    • Disable BGP layer: "bgpMeasurements": false

  • http-server - Create HTTP Server test

    • Disable BGP layer: "bgpMeasurements": false

    • Disable Network layer: "networkMeasurements": false

  • page-load - Create Page Load test

    • Disable BGP layer: "bgpMeasurements": false

    • Disable Network layer: "networkMeasurements": false

  • web-transaction - Create Web Transactions test

    • Disable BGP layer: "bgpMeasurements": false

    • Disable Network layer: "networkMeasurements": false

  • api - Create API test

    • Disable BGP layer: "bgpMeasurements": false

    • Disable Network layer: "networkMeasurements": false

  • ftp - Create FTP Server test

    • Disable BGP layer: "bgpMeasurements": false

    • Disable Network layer: "networkMeasurements": false

  • sip - Create SIP Server test

    • Disable BGP layer: "bgpMeasurements": false

    • Disable Network layer: "networkMeasurements": false

  • rtp - Create RTP test

    • Disable BGP layer: "bgpMeasurements": false

    • Disable Network layer: "networkMeasurements": false

Limitations

  • Maximum 10 streams per account group and data model version.

  • Shared tests are not supported.

  • Traces are supported with data model v2 only.

Last updated