# Streaming Connected Devices Test Metrics to Google Pub/Sub This guide covers how to stream Cisco ThousandEyes Connected Devices test metrics to Google Pub/Sub for use in your data analytics applications and workflows. Google Pub/Sub is a messaging service that can integrate with ThousandEyes Connected Devices, enabling real-time data streaming to Google Cloud for advanced analytics, automation, and visualization. Once you have set up Google Pub/Sub environment to receive data from ThousandEyes Connected Devices, ThousandEyes configures the pipeline to deliver Connected Devices test metrics to the designated topics. For more information about Connected Devices, see [Connected Devices](https://docs.thousandeyes.com/product-documentation/connected-devices). To learn more about Google Pub/Sub, see [Google Pub/Sub](https://cloud.google.com/pubsub). ## Use Cases for Integrating Connected Devices with Google Pub/Sub Streaming ThousandEyes Connected Devices test metrics to Google Pub/Sub enables scalable, real-time data ingestion and processing. Streaming ThousandEyes Connected Devices test metrics to Google Pub/Sub can be used for: * **Advanced data analytics:** Stream ThousandEyes Connected Devices test metrics to Pub/Sub for real-time ingestion into analytics pipelines, enabling deeper insights through correlation with other data sources, anomaly detection, and predictive modeling. * **Custom visualizations and dashboards:** Feed streamed metrics into visualization tools via Pub/Sub subscriptions, creating tailored, interactive dashboards that extend ThousandEyes' views with multi-source data overlays for holistic monitoring. * **Integration with existing applications:** Use Pub/Sub as middleware to seamlessly connect ThousandEyes Connected Devices test metrics with enterprise systems, enabling event-driven architectures where network data triggers automated workflows or enriches existing tools without custom coding. For example, you can: * Leverage Google Cloud’s native integrations to stream Pub/Sub data directly into BigQuery, enabling advanced analytics such as real-time querying, trend analysis, and machine learning on ThousandEyes Connected Devices test metrics like latency and packet loss. * Utilize Google Cloud Managed Service for Prometheus to collect and query metrics from Pub/Sub streams, then connect visualization tools like Grafana for custom dashboards that provide interactive, multi-source views of network performance. * Employ third-party add-ons or apps to integrate ThousandEyes Connected Devices test data with existing applications, facilitating unified logging, alerting, and correlation across network and application domains. ### Add-on Support for Integrating Connected Devices with Google Cloud Google Cloud Platform supports a number of add-ons that can be used to integrate ThousandEyes Connected Devices test data with your existing applications. For example, to give Splunk access to your ThousandEyes Connected Devices test metrics, you can use the [Splunk Add-on for Google Cloud Platform](https://splunk.github.io/splunk-add-on-for-google-cloud-platform/). ## Supported Tests for Streaming Connected Devices Data to Google Pub/Sub Cisco ThousandEyes Connected Devices makes the following tests available for streaming to Google Pub/Sub: | Test | Description | Related Documentation | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | httpget | Measures download performance using HTTP GET requests to fetch data from a server. | [Speed Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/speed-tests) | | httppost | Measures upload performance using HTTP POST requests to send data to a server. | [Speed Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/speed-tests) | | udplatency | Measures the round-trip time (RTT) of small UDP packets between the device and a target server, including mean, min, max, and standard deviation. | [Latency, Loss, Disconnections, and Jitter Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/latency-loss-disconnections-jitter-tests) | | udpjitter | Measures packet delay variation (jitter) using a bi-directional UDP stream simulating VoIP conditions, recording RTT, loss, and jitter. | [Latency, Loss, Disconnections, and Jitter Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/latency-loss-disconnections-jitter-tests) | | udplatency (ping) | Measures RTT using ICMP echo request packets, similar to UDP latency but using ICMP protocol. | [Latency, Loss, Disconnections, and Jitter Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/latency-loss-disconnections-jitter-tests) | | tt-httpget | Throughput measurement during HTTP GET-based download tests, focusing on data transfer rates over time. | [Speed Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/speed-tests) | | tt-httppost | Throughput measurement during HTTP POST-based upload tests, focusing on data transfer rates over time. | [Speed Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/speed-tests) | | tt-udpjitter | Throughput or performance measurement under jitter test conditions using UDP streams. | [Latency, Loss, Disconnections, and Jitter Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/latency-loss-disconnections-jitter-tests) | | realspeed-download | Measures actual download speed from the router and personal device to the internet for performance comparison. | [Cisco Real Speed](https://docs.thousandeyes.com/product-documentation/connected-devices/cisco-real-speed) | | realspeed-upload | Measures actual upload speed from the router and personal device to the internet for performance comparison. | [Cisco Real Speed](https://docs.thousandeyes.com/product-documentation/connected-devices/cisco-real-speed) | | realspeed-jitter | Measures jitter during real speed tests on the router-to-internet path. | [Cisco Real Speed](https://docs.thousandeyes.com/product-documentation/connected-devices/cisco-real-speed) | | disconnection | Detects complete loss of connectivity, recorded as consecutive packet losses to all servers. | [Latency, Loss, Disconnections, and Jitter Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/latency-loss-disconnections-jitter-tests) | | partial\_disconnection | Detects partial loss of connectivity, such as consecutive packet losses to specific servers. | [Latency, Loss, Disconnections, and Jitter Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/latency-loss-disconnections-jitter-tests) | | udp\_accelerated\_download | Measures high-speed download throughput using hardware-accelerated UDP streams. | [Speed Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/speed-tests) | | udp\_accelerated\_upload | Measures high-speed upload throughput using hardware-accelerated UDP streams. | [Speed Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/speed-tests) | | tt\_udp\_accelerated\_download | Throughput measurement during hardware-accelerated UDP download tests. | [Speed Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/speed-tests) | | tt\_udp\_accelerated\_upload | Throughput measurement during hardware-accelerated UDP upload tests. | [Speed Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests/network/speed-tests) | For a list of Connected Devices test metrics available for Google Pub/Sub, see the section [Metrics Definitions for Streaming Connected Devices Test Data to Google Pub/Sub](#metrics-definitions-for-streaming-connected-devices-test-data-to-google-pubsub). To learn more about available Connected Devices test metrics, see [Connected Devices Tests](https://docs.thousandeyes.com/product-documentation/connected-devices/connected-devices-tests). ## Requirements for Integrating Connected Devices with Google Pub/Sub ### Designate Google Pub/Sub Topics for Use with ThousandEyes Integrating Cisco ThousandEyes Connected Devices test metrics with Google Pub/Sub requires you to grant ThousandEyes `Publisher` access to Google Pub/Sub topics designated for this purpose. To learn more about setting up topics in Google Pub/Sub, see the section [Creating Google Pub/Sub Topics](#creating-google-pubsub-topics). ### Grant ThousandEyes Access to Google Pub/Sub When you grant ThousandEyes `Publisher` access to a Google Pub/Sub topic, ThousandEyes can publish messages to the specified topic and view topic metadata. This allows ThousandEyes to send Connected Devices test metrics to the topic it is assigned to. ThousandEyes cannot read messages, manage subscriptions, or modify the topic. ThousandEyes can only publish data to the topic/s it is assigned to. For more details, see [Google Cloud’s Pub/Sub IAM documentation](https://cloud.google.com/pubsub/docs/access-control). Granting ThousandEyes access to Google Pub/Sub topics is a manual process. There are two ways you can grant ThousandEyes access, both require you to contact your account representative: * Request a service account email. * Securely share the credentials file for a Google Cloud service account with write access to the Google Pub/Sub topics you want to use with ThousandEyes Connected Devices. For more information on granting ThousandEyes access to Google Pub/Sub topics, see the section [Granting ThousandEyes Access to Google Pub/Sub](#granting-thousandeyes-access-to-google-pubsub). ### Notify ThousandEyes Once you have granted ThousandEyes access to your Google Pub/Sub topics, you will need to contact your account representative. For instructions on how to notify ThousandEyes and complete your integration, see the section [Notifying ThousandEyes When Access is Granted](#notifying-thousandeyes-when-access-is-granted). ## Setting Up Streaming ### Creating Google Pub/Sub Topics Create Google Pub/Sub topics according to how you want to organize the Connected Devices test metric data you receive from Cisco ThousandEyes. You can use a single topic for all metrics (e.g. network-metrics) or you can use separate topics for each metric type (e.g. download-metrics, upload-metrics, latency-metrics). To create topics in Google Pub/Sub, see [Create a Topic](https://cloud.google.com/pubsub/docs/create-topic#create_a_topic_2). ### Granting ThousandEyes Access to Google Pub/Sub There are two ways to grant ThousandEyes access to publish test metrics to your Google Pub/Sub topics. You can use a: * Service account email provided by ThousandEyes * Service account key shared securely with ThousandEyes #### Grant ThousandEyes Access to Google Pub/Sub Using a Service Account Email 1. Contact your account manager to request the ThousandEyes service account email. 2. Navigate to **Google Cloud Console > Pub/Sub > Topics**. 3. Select a topic (e.g., download-metrics) and click **Permissions**. 4. Click **Add Principal** and enter the ThousandEyes service account email. 5. Assign the role `Pub/Sub Publisher` to the service account. 6. Save the changes. 7. Repeat the process for the other topics (e.g., upload-metrics, latency-metrics). ThousandEyes Connected Devices now has permission to write test data to the Pub/Sub topics you have granted it access to. #### Grant ThousandEyes Access to Google Pub/Sub Using a Service Key A Google Cloud Platform (GCP) service account key is a JSON credential file that authenticates ThousandEyes to securely publish Connected Devices test metrics to a Pub/Sub topic. To learn more about creating and managing service account keys, see [Create and delete service account keys](https://cloud.google.com/iam/docs/keys-create-delete). Contact your account manager for options to securely share the service account key with ThousandEyes. ### Notifying ThousandEyes When Access is Granted When you have completed the steps to grant ThousandEyes access to your Google Pub/Sub topics, contact your account manager and provide the following information: * Pub/Sub topic names: (e.g., download-metrics, upload-metrics, latency-metrics). * Confirmation that you have granted their service account Pub/Sub `Publisher` access to these topics. Once this information has been received by your account manager, ThousandEyes will manually set up publishing. We will notify you when this is complete. ## Frequently Asked Questions ### What happens if I want to stream data to AWS services (e.g., SQS)? Currently, only Google Pub/Sub is supported by ThousandEyes Connected Devices. OTel support is presently under development. ### Can I configure the frequency of data syncs? No, the data is streamed in real-time as it is processed by the ThousandEyes pipeline. There is no manual configuration for sync frequency. ### What if I need support for additional metrics or platforms? Future support for additional metrics and platforms like OpenTelemetry may be added based on customer demand. ### Could I get access to sample messages? You can reach out to your account manager for a set of sample messages. ## Metrics Definitions for Streaming Connected Devices Test Data to Google Pub/Sub Below is a list of fields and descriptions for the tests supported in the Cisco ThousandEyes Connected Devices test metrics pipeline. Please note that this list may grow over time. For the most up-to-date list of data fields, including data types, reach out to your account manager. ### httpget Test Fields | Field | Description | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | bytes\_sec\_interval | Throughput at this specific interval. In the US, we report only a single interval, so value matches bytes\_sec. | | warmup\_time | Time consumed for all the TCP streams to arrive at optimal window size (Units: microseconds) | | threads | The number of concurrent TCP connections used in the test | | bytes\_total | Total bytes downloaded across all connections | | fetch\_time | Time the test ran for in microseconds | | sequence | The interval that this row refers to (in the US, this is always 0, as we report only one interval of 10 seconds) | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | | ip\_version | IP protocol version used for this test | | tcp\_retransmissions | Number of TCP Retransmissions during this test | | warmup\_bytes | Bytes transferred for all the TCP streams during the warm-up phase | *** ### httppost Test Fields | Field | Description | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | bytes\_sec\_interval | Throughput at this specific interval. In the US, we report only a single interval, so value matches bytes\_sec. | | warmup\_time | Time consumed for all the TCP streams to arrive at optimal window size (Units: microseconds) | | threads | The number of concurrent TCP connections used in the test | | bytes\_total | Total bytes uploaded across all connections | | fetch\_time | Time the test ran for in microseconds | | sequence | The interval that this row refers to (in the US, this is always 0, as we report only one interval of 10 seconds) | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | | ip\_version | IP protocol version used for this test | | tcp\_retransmissions | Number of TCP Retransmissions during this test | | warmup\_bytes | Bytes transferred for all the TCP streams during the warm-up phase | *** ### udplatency Test Fields | Field | Description | | ------------- | ----------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (note: use failures/(successes+failures) for packet loss) | | failures | Number of failures (packets lost) | | mac | Unit MAC address | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | ip\_version | IP protocol version used for this test | | rtt\_avg | Average RTT in microseconds | | rtt\_min | Minimum RTT in microseconds | | rtt\_max | Maximum RTT in microseconds | | rtt\_std | Standard Deviation in Measured RTT in microseconds | *** ### udpjitter Test Fields | Field | Description | | ------------------- | ------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | ip\_version | IP protocol version used for this test | | packet\_size | Size of each UDP Datagram (Units: Bytes) | | stream\_rate | Rate at which the UDP stream is generated (Units: bits/sec) | | duration | Total duration of test (Units: microseconds) | | packets\_up\_sent | Number of packets sent in Upstream (measured by client) | | packets\_down\_sent | Number of packets sent in Downstream (measured by server) | | packets\_up\_recv | Number of packets received in Upstream (measured by server) | | packets\_down\_recv | Number of packets received in Downstream (measured by client) | | jitter\_up | Upstream Jitter measured (Units: microseconds) | | jitter\_down | Downstream Jitter measured (Units microseconds) | | latency | 99th percentile of round trip times for all packets | | mos | Mean Opinion Score calculated for the test | *** ### udplatency (ping) Test Fields | Field | Description | | ------------- | ----------------------------------------------------------------------------- | | unit\_id | Unique identifier for an individual unit | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | base | Hardware type for an individual unit | | successes | Number of successes (note: use failures/(successes+failures) for packet loss) | | failures | Number of failures (packets lost) | | mac | Unit MAC address | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | ip\_version | IP protocol version used for this test | | rtt\_avg | Average RTT in microseconds | | rtt\_min | Minimum RTT in microseconds | | rtt\_max | Maximum RTT in microseconds | | rtt\_std | Standard Deviation in Measured RTT in microseconds | *** ### tt-httpget Test Fields | Field | Description | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | test\_id | Unique identifier for an individual test run | | testing\_user\_id | Optional ID of the user that initiated this test | | test\_source | Optional application source of the measurement | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | bytes\_sec\_interval | Throughput at this specific interval. In the US, we report only a single interval, so value matches bytes\_sec. | | warmup\_time | Time consumed for all the TCP streams to arrive at optimal window size (Units: microseconds) | | threads | The number of concurrent TCP connections used in the test | | bytes\_total | Total bytes downloaded across all connections | | fetch\_time | Time the test ran for in microseconds | | sequence | The interval that this row refers to (in the US, this is always 0, as we report only one interval of 10 seconds) | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | | ip\_version | IP protocol version used for this test | | tcp\_retransmissions | Number of TCP Retransmissions during this test | | warmup\_bytes | Bytes transferred for all the TCP streams during the warm-up phase | *** ### tt-httppost Test Fields | Field | Description | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | test\_id | Unique identifier for an individual test run | | testing\_user\_id | Optional ID of the user that initiated this test | | test\_source | Optional application source of the measurement | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | bytes\_sec\_interval | Throughput at this specific interval. In the US, we report only a single interval, so value matches bytes\_sec. | | warmup\_time | Time consumed for all the TCP streams to arrive at optimal window size (Units: microseconds) | | threads | The number of concurrent TCP connections used in the test | | bytes\_total | Total bytes uploaded across all connections | | fetch\_time | Time the test ran for in microseconds | | sequence | The interval that this row refers to (in the US, this is always 0, as we report only one interval of 10 seconds) | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | | ip\_version | IP protocol version used for this test | | tcp\_retransmissions | Number of TCP Retransmissions during this test | | warmup\_bytes | Bytes transferred for all the TCP streams during the warm-up phase | *** ### tt-udpjitter Test Fields | Field | Description | | ------------------- | ------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | test\_id | Unique identifier for an individual test run | | testing\_user\_id | Optional ID of the user that initiated this test | | test\_source | Optional application source of the measurement | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | ip\_version | IP protocol version used for this test | | packet\_size | Size of each UDP Datagram (Units: Bytes) | | stream\_rate | Rate at which the UDP stream is generated (Units: bits/sec) | | duration | Total duration of test (Units: microseconds) | | packets\_up\_sent | Number of packets sent in Upstream (measured by client) | | packets\_down\_sent | Number of packets sent in Downstream (measured by server) | | packets\_up\_recv | Number of packets received in Upstream (measured by server) | | packets\_down\_recv | Number of packets received in Downstream (measured by client) | | jitter\_up | Upstream Jitter measured (Units: microseconds) | | jitter\_down | Downstream Jitter measured (Units microseconds) | | latency | 99th percentile of round trip times for all packets | | mos | Mean Opinion Score calculated for the test | *** ### realspeed-download Test Fields | Field | Description | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | test\_id | Unique identifier for an individual test run | | testing\_user\_id | Optional ID of the user that initiated this test | | triggering\_agent\_id | Unique identifier for the user's device (e.g. phone, browser) | | agent\_id | An internal agent identifier for the unit (Whitebox) | | target | The test server in use | | address | The IP address of the server (resolved by the client's DNS) | | ip\_version | Whether IPv4 or IPv6 was used for this test | | fetch\_time | Time the test ran for in microseconds | | bytes\_total | Total bytes downloaded across all connections | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | | bytes\_sec\_interval | Throughput at this specific interval. In the US, we report only a single interval, so value matches bytes\_sec. | | warmup\_time | Time consumed for all the TCP streams to arrive at optimal window size (Units: microseconds) | | warmup\_bytes | Bytes transferred for all the TCP streams during the warm-up phase | | sequence | The interval that this row refers to (in the US, this is always 0, as we report only one interval of 10 seconds) | | threads | The number of concurrent TCP connections used in the test | | tcp\_retransmissions | Number of TCP Retransmissions during this test | | web\_duration | Time the test ran for in the web browser test in microseconds | | web\_bytes\_total | Total bytes downloaded in the web browser test across all connections | | web\_bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the web browser test to the current interval | | web\_successes | Number of successes for the web browser test (always 1 or 0 for this test) | | web\_failures | Number of failures for the web browser test (always 1 or 0 for this test) | *** ### realspeed-upload Test Fields | Field | Description | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | test\_id | Unique identifier for an individual test run | | testing\_user\_id | Optional ID of the user that initiated this test | | triggering\_agent\_id | Unique identifier for the user's device (e.g. phone, browser) | | agent\_id | An internal agent identifier for the unit (Whitebox) | | target | The test server in use | | address | The IP address of the server (resolved by the client's DNS) | | ip\_version | Whether IPv4 or IPv6 was used for this test | | fetch\_time | Time the test ran for in microseconds | | bytes\_total | Total bytes downloaded across all connections | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | | bytes\_sec\_interval | Throughput at this specific interval. In the US, we report only a single interval, so value matches bytes\_sec. | | warmup\_time | Time consumed for all the TCP streams to arrive at optimal window size (Units: microseconds) | | warmup\_bytes | Bytes transferred for all the TCP streams during the warm-up phase | | sequence | The interval that this row refers to (in the US, this is always 0, as we report only one interval of 10 seconds) | | threads | The number of concurrent TCP connections used in the test | | tcp\_retransmissions | Number of TCP Retransmissions during this test | | web\_duration | Time the test ran for in the web browser test in microseconds | | web\_bytes\_total | Total bytes downloaded in the web browser test across all connections | | web\_bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the web browser test to the current interval | | web\_successes | Number of successes for the web browser test (always 1 or 0 for this test) | | web\_failures | Number of failures for the web browser test (always 1 or 0 for this test) | *** ### realspeed-jitter Test Fields | Field | Description | | --------------------- | --------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | test\_id | Unique identifier for an individual test run | | testing\_user\_id | Optional ID of the user that initiated this test | | triggering\_agent\_id | Unique identifier for the user's device (e.g. phone, browser) | | agent\_id | An internal agent identifier for the unit (Whitebox) | | target | The test server in use | | address | The IP address of the server (resolved by the client's DNS) | | ip\_version | Whether IPv4 or IPv6 was used for this test | | packet\_size | Size of each UDP Datagram (Units: Bytes) | | stream\_rate | Rate at which the UDP stream is generated (Units: bits/sec) | | duration | Total duration of test (Units: microseconds) | | packets\_up\_sent | Number of packets sent in Upstream (measured by client) | | packets\_down\_sent | Number of packets sent in Downstream (measured by server) | | packets\_up\_recv | Number of packets received in Upstream (measured by server) | | packets\_down\_recv | Number of packets received in Downstream (measured by client) | | jitter\_up | Upstream Jitter measured (Units: microseconds) | | jitter\_down | Downstream Jitter measured (Units microseconds) | | latency | 99th percentile of round trip times for all packets | | mos | Mean Opinion Score | | web\_rtt | Average round-trip time for the browser portion of the test (Units: microseconds) | | web\_jitter | Average jitter for the browser portion of the test (Units: microseconds) | | web\_duration | Duration of the browser portion of the test (Units: microseconds) | | web\_successes | Number of successes for the browser portion of the test | | web\_failures | Number of failures for the browser portion of the test | *** ### disconnection Test Fields | Field | Description | | --------------- | -------------------------------------------------------------------------------------------------- | | dtime | Start of the disconnection in units timezone | | dtime\_utc | Start of the disconnection in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | mac | Unit MAC address | | agent\_id | An internal agent identifier for the unit (Whitebox) | | detected\_by | Whether the disconnection was detected by client or server. | | target | Only set when detected by client | | address | The IP address of the server (resolved by the client's DNS) - only present when detected by client | | end\_dtime | End of the disconnection in units timezone | | end\_dtime\_utc | End of the disconnection in UTC | | duration | Total duration of the disconnection in seconds | | packets | The number of packets lost in a row - only present when detected by client | *** Here are the markdown tables for the requested Connected Devices tests: *** ### partial\_disconnection Test Fields | Field | Description | | ------------- | -------------------------------------------------------------------------- | | dtime | Start of the disconnection in units timezone | | dtime\_utc | Start of the disconnection in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | mac | Unit MAC address | | type | Can be "connection" or "disconnection" | | controller | The trigger testing controller that the unit has connected/disconnected to | *** ### udp\_accelerated\_download Test Fields | Field | Description | | ------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | packet\_size | Size of each UDP Datagram (Units: Bytes) | | stream\_rate | Rate at which the UDP stream is generated (Units: bits/sec) | | bytes\_total | Total bytes downloaded across all connections | | duration | Total duration of test (Units: microseconds) | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | *** ### udp\_accelerated\_upload Test Fields | Field | Description | | ------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | packet\_size | Size of each UDP Datagram (Units: Bytes) | | stream\_rate | Rate at which the UDP stream is generated (Units: bits/sec) | | bytes\_total | Total bytes downloaded across all connections | | duration | Total duration of test (Units: microseconds) | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | *** ### tt\_udp\_accelerated\_download Test Fields | Field | Description | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | packet\_size | Size of each UDP Datagram (Units: Bytes) | | stream\_rate | Rate at which the UDP stream is generated (Units: bits/sec) | | bytes\_total | Total bytes downloaded across all connections | | duration | Total duration of test (Units: microseconds) | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | | test\_id | Unique identifier for an individual test run | | testing\_user\_id | Optional ID of the user that initiated this test | | test\_source | Optional application source of the measurement | *** ### tt\_udp\_accelerated\_upload Test Fields | Field | Description | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | dtime | Time test finished in the unit’s local time | | dtime\_utc | Time test finished in UTC | | processed\_at | Time the test was processed by SK in UTC | | unit\_id | Unique identifier for an individual unit | | base | Hardware type for an individual unit | | successes | Number of successes (always 1 or 0 for this test) | | failures | Number of failures (always 1 or 0 for this test) | | mac | Unit MAC address | | target | Target hostname or IP address | | address | The IP address of the server (resolved by the client's DNS) | | packet\_size | Size of each UDP Datagram (Units: Bytes) | | stream\_rate | Rate at which the UDP stream is generated (Units: bits/sec) | | bytes\_total | Total bytes downloaded across all connections | | duration | Total duration of test (Units: microseconds) | | bytes\_sec | Running total of throughput, sum of speeds measured for each stream (in bytes/sec), from the start of the test to the current interval | | test\_id | Unique identifier for an individual test run | | testing\_user\_id | Optional ID of the user that initiated this test | | test\_source | Optional application source of the measurement | httpget httppost udplatency udpjitter udplatency (ping) tt-httpget tt-httppost tt-udpjitter realspeed-download realspeed-upload realspeed-jitter disconnection partial\_disconnection udp\_accelerated\_download udp\_accelerated\_upload tt\_udp\_accelerated\_download tt\_udp\_accelerated\_upload