Skip to content

Self-built Node Management


In addition to the built-in nodes of the TrueWatch system, you can also create new testing nodes anywhere in the world. By establishing self-built nodes across different geographic locations and with different ISPs, you can monitor availability from multiple regions and gain a comprehensive understanding of your site's availability.

Create Node

Go to Synthetic Tests > Self-built Node Management and click Create.

  1. Select the country/region and province or city.
  2. Select the ISP.
  3. The node code will be automatically filled in; the node code cannot be duplicated within the current workspace.
  4. Enter the node name; the node name cannot be duplicated within the current workspace.
  5. Click Confirm.

Manage Node

In the node list, you can uniformly view and manage all self-built nodes in the current workspace through the following operations:

  • Click "Get Configuration" to directly copy the configuration information from the pop-up window.
  • Click "Operation Audit" to view the operation records related to this node.
  • Click "Delete" to remove the current node. If a self-built node is associated with a testing task, after deletion, this node will no longer report data for that task, but the data already reported will not be affected.

Install Node

After creating a node, install DataKit on a host that can reach the test target, then configure the dialtesting collector. The host must also be able to reach the configured server and the DataKit data ingestion endpoint.

Host Deployment

The collector configuration file is <DataKit installation directory>/conf.d/samples/dialtesting.conf. With the default installation paths, the file is:

Operating System Configuration File
Linux / macOS /usr/local/datakit/conf.d/samples/dialtesting.conf
Windows 64-bit C:\Program Files\datakit\conf.d\samples\dialtesting.conf

For other installation paths, see DataKit Installation Directories.

  1. In Self-built Node Management > Get Configuration, copy the node's server, region_id, ak, and sk.
  2. Open conf.d/samples under the DataKit installation directory and copy dialtesting.conf.sample to dialtesting.conf. If the node is already configured, edit the existing file instead of overwriting it or creating a duplicate configuration.
  3. In the [[inputs.dialtesting]] section, replace the existing values with those provided by the console and retain the other settings. Replace all placeholders below with actual values. Do not put this configuration in datakit.conf:

    [[inputs.dialtesting]]
      server = "<SERVER>"
      region_id = "<REGION_ID>"
      ak = "<AK>"
      sk = "<SK>"
    

    To test private network addresses, also set disable_internal_network_task = false in the same [[inputs.dialtesting]] section.

  4. Save the file and restart DataKit. For DataKit 2.1.0 and later, use datakit service restart; Linux / macOS may require sudo. For other versions, refer to the corresponding service management commands.

  5. Select this self-built node in a test task. After the task runs, check the reported results in the Test Explorer.

For Kubernetes deployment and the full configuration reference, see Dialtesting Collector Configuration.

Billing

Tests run on self-built nodes incur both execution and data storage charges. The billable execution count is 1/10 of the public-node count: each Browser Test execution counts as 1 billable execution, and each execution of other test types counts as 0.1 billable executions.

See Synthetic Monitoring Billing for metering rules and Commercial Plan Billing Details for unit prices.