ThousandEyes for OpenTelemetry Data Model v2 - Metrics
Supported Test Types
CEA (Cloud and Enterprise Agents)
Test Type | Metrics | Specific Resource Attributes | Specific Metric Attributes |
HTTP server |
|
|
|
Agent-to-server |
|
|
|
Agent-to-agent Agent-to-agent (unidirectional or bidirectional) |
|
|
|
BGP |
|
| |
Transaction |
|
| |
DNS server |
|
|
|
DNSSEC |
|
|
|
DNS trace |
|
|
|
Page load |
|
|
|
FTP server |
|
|
|
SIP server |
|
|
|
RTP stream |
|
|
|
API test |
| ||
API test per step |
|
|
|
Endpoint Agents
Test Type | Metrics | Specific Resource Attributes | Specific Metric Attributes |
HTTP server |
|
|
|
Agent-to-server |
|
|
|
Metrics
Key | Data Type | Description |
| Double (Percentage) | Calculated depending on the errors reported during the test. In case there is any error, the availability is 0, otherwise 100%. |
| Double (Bytes-per-second) | Throughput of test in bytes/second. |
| Double (Seconds) | Time-to-first-byte as measured in the client. |
| Double (Seconds) | The maximum round trip time for the packets sent to the target. |
| Double (Percentage) | Packet loss. |
| Double (Milliseconds) | Standard deviation for the round trip times. |
| Double (Seconds) | The time it took the transaction to complete successfully. This metric is not exposed if there are errors. |
| Double (Percentage) | Percentage of completion of the transaction. 100% if the transaction completes successfully, 0% if there are errors. |
| Integer (count) | Determines whether there were errors or not. 1 if there’s an error processing the transaction, 0 if not. |
| Double (Percentage) | Calculated depending on the errors reported during the test. If there is any error, the availability is 0, otherwise 100%. |
| Double (Seconds) | DNS resolve time. |
| Double (Percentage) | Calculated depending on the errors reported during the test. If there is any error, the validity is 0, otherwise 100%. |
| Double (Percentage) | Calculated depending on the errors reported during the test. If there is any error, the validity is 0, otherwise 100%. |
| Double (Seconds) | Time to completely load the page. |
| Double (Percentage) | Calculated depending on the errors reported during the test. If there is any error, the availability is 0, otherwise 100%. |
| Integer (Bytes-per-second) | Throughput of test in bytes/second. |
| Double (Seconds) | Total time it took to get the first byte while executing the request. |
| Double (Percentage) | Calculated depending on the errors reported during the test. If there is any error, the availability is 0, otherwise 100%. |
| Double (Seconds) | Total time it took to get the first byte while executing the request. |
| Double (Seconds) | Total time it took until the last response was received. |
| Double (score) | Mean opinion score (MOS). A measurement of perceived voice quality, ranging from 1 to 5. A MOS of 5 indicates excellent voice call quality, while a MOS of 1 indicates poor voice call quality. |
| Double (Percentage) | Percentage of frames lost computed from lost frames count and total frames. |
| Double (Percentage) | Percentage of frames discarded computed from discarded frames count and total frames. |
| Double (Seconds) | Total time it took for the test round execution. |
| Long (Seconds) | Packet delay variation. |
| Integer (count) | Number of BGP route changes. |
| Double (Percentage) | Whether BGP route target is reachable. |
| Integer (count) | Number of BGP updates. |
| Double (Seconds) | The time the entire API test took to run, including all steps. |
| Double (Percentage) | Percentage of completion of all the steps of the API test. |
| Double (Seconds) | The time it took the API test to complete the step. |
| Double (Percentage) | Percentage of completion of the step of the API test. 100% if the step is completed successfully, 0% if there are errors. |
Attributes
The OpenTelemetry pipeline supports the following OTel attributes:
Common Resource Attributes
Key | Data Type | Description |
| String | UUID of the integration used to route the data point to the external service. |
| String | The ID of the account that the telemetry data is associated with. |
| String | Identifies the origin of the test data. Possible values: |
| String | Identifies the ThousandEyes test. |
| String | The name of the ThousandEyes test. |
| String | Identifies the type of test. Possible values: |
| String | Identifies the ThousandEyes agent that ran the test. Note: This attribute is not part of BGP metrics. |
| String | Agent location. Note: This attribute is not part of BGP metrics. |
| String | Agent name. Note: This attribute is not part of BGP metrics. |
| String | Specifies the version of the data model. Possible values:
|
| String | URL for the network test instance that generated the data. |
Tags as Attributes
Any tag associated with the test is transformed into an attribute of the Resource
.
Each tag is defined by a key
and a value
. For instance, you might have tags such as branch:sfo
, branch:nyc
and team:netops
When a tag is converted to an attribute:
If there are several values for the same key, the attribute value will be represented as an array containing the
string
elements that are the values associated with the tag'skey
.If there is only one value for the key, the attribute value will be represented as
string
.
For the tag examples above, the resulting attribute would be structured as follows:
Note that not all observability platforms accommodate the use of string arrays for attribute values. For instance, New Relic does not support this format. If your backend does not support string arrays for attributes, the tag attribute is excluded from the metric.
Specific Resource Attributes
Key | Data Type | Description |
| String | Server domain name if available without reverse DNS lookup; otherwise, IP address or Unix domain socket name. |
| Integer | Server port number. |
| String | The URI scheme component identifies the used protocol. Enum:
|
| String | HTTP request method. Enum:
|
| String | The matched route. |
| String | OSI transport layer or inter-process communication method. Enum:
|
| String | Identifies the ThousandEyes agent that was the target of the test. |
| String | Target agent location. |
| String | Target agent name. |
| String | The network IO operation direction.Enum:
|
| String | The name being queried. |
| String | A BGP prefix includes the IP address and the subnet mask. It is assigned to a particular network |
| String | The ID of the BGP monitor. The monitor collects BGP data from different Autonomous Systems (AS) around the world to understand how routes are being propagated. |
| String | The name of the BGP monitor. |
| String | The location of the BGP monitor. |
| String | FTP request method. Enum:
|
| Integer | The API step ID. |
Specific Metric Attributes
Key | Data Type | Description |
| String | Describes a class of error the operation ended with. |
| Integer | HTTP response status code |
| Integer | FTP response status code |
| Integer | SIP response status code |
Metric Unit
Name | Value | Type |
Count |
| Integer |
Error Count |
| Integer |
(BGP) Path Changes Count |
| Integer |
(BGP) Updates Count |
| Integer |
Score |
| Double |
Milliseconds |
| Double |
Seconds |
| Double |
Percentage |
| Double |
Bytes-per-second |
| Integer |
Last updated