> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application-1/sa-6/features/network-test.md).

# Network Test

A Support Application 6 feature that tests reachability and latency against configured endpoints and fires a Network Test event.

## Overview

Use Network Test to test reachability and latency against configured endpoints, independent of the throughput-focused Speed Test. Network Test can run on demand from the device, on a schedule, or remotely from the Portal, and fires a `networktestevent` with the results.

Scheduled runs are disabled by default.&#x20;

## User Guide

1. Configure endpoint URLs.
2. Enable scheduled runs, if needed.
3. Set the schedule interval.
4. Select which endpoints to include in scheduled tests.

## Configuration&#x20;

### Configuring Endpoint URLs

To specify the BlueFletch-provided endpoints to test, add `bfUrls` to the `networkTest` configuration:

```json
"bfSupportAgent": {
  "networkTest": {
    "bfUrls": [
      "https://ems-api.bluefletch.com"
    ]
  }
}
```

To specify org-provided endpoints to test, add `orgUrls` to the `networkTest` configuration:

```json
"bfSupportAgent": {
  "networkTest": {
    "orgUrls": [
      "https://example.com/api"
    ]
  }
}
```

### Enabling Scheduled Runs

To enable scheduled, non-interactive runs, add a `periodicNetworkTest` configuration section with enable set to `true`:

```json
"bfSupportAgent": {
  "periodicNetworkTest": {
    "enable": true
  }
}
```

### Configuring Schedule Interval

To set the interval between scheduled runs, add interval in hours to the `periodicNetworkTest` configuration. The value is clamped to 2–24 hours. The default is `4`:

```json
"bfSupportAgent": {
  "periodicNetworkTest": {
    "interval": 6
  }
}
```

### Selecting Scheduled Test Endpoints

To include BlueFletch endpoints in the scheduled test set, add `bfEndpoints` to the `periodicNetworkTest` configuration:

```json
"bfSupportAgent": {
  "periodicNetworkTest": {
  "bfEndpoints": true
  }
}
```

To include org endpoints in the scheduled test set, add `orgEndpoints` to the `periodicNetworkTest` configuration:

```json
"bfSupportAgent": {
  "periodicNetworkTest": {
    "orgEndpoints": true
  }
}
```

If neither `bfEndpoints` nor `orgEndpoints` is set, BlueFletch endpoints are used by default.

The Network Test configuration consists of the following parameters:

| **Configuration**                  | **Type**        | **Default** | **Description**                                                                                                                            |
| ---------------------------------- | --------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `networkTest.bfUrls`               | String array    | —           | BlueFletch-provided endpoint URLs to test                                                                                                  |
| `networkTest.orgUrls`              | String array    | —           | Org-provided endpoint URLs to test                                                                                                         |
| `periodicNetworkTest.enable`       | Boolean         | —           | Enables scheduled (non-interactive) runs                                                                                                   |
| `periodicNetworkTest.interval`     | Integer (hours) | 4           | Interval between scheduled runs, clamped to 2–24 hours                                                                                     |
| `periodicNetworkTest.bfEndpoints`  | Boolean         | —           | Include BlueFletch endpoints in the scheduled test set                                                                                     |
| `periodicNetworkTest.orgEndpoints` | Boolean         | —           | Include org endpoints in the scheduled test set. If neither bfEndpoints nor orgEndpoints is set, BlueFletch endpoints are used by default. |

## Putting It All Together

For the example described above, the full configuration for the Network Test feature is as follows:

```json
"bfSupportAgent": {
 "networkTest": {
   "bfUrls": [
     "https://ems-api.bluefletch.com"
   ],
   "orgUrls": [
     "https://example.com/api"
   ]
 },
 "periodicNetworkTest": {
   "enable": true,
   "interval": 6,
   "bfEndpoints": true,
   "orgEndpoints": true
 }
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application-1/sa-6/features/network-test.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
