📣
TiDB Cloud Essential is now in public preview. Try it out →

Telemetry




When the telemetry feature is enabled, TiUP collects usage information and shares the information with PingCAP to help understand how to improve the product.

What is shared when telemetry is enabled?

The following sections describe the shared usage information in detail for TiUP. The usage details that get shared might change over time. These changes (if any) will be announced in release notes.

When the telemetry collection feature is enabled in TiUP, usage details of TiUP will be shared, including (but not limited to):

  • A randomly generated telemetry ID.
  • Execution status of TiUP commands, such as whether the execution is successful and the execution duration.
  • Deployment characteristics, such as the size of hardware, TiDB components versions, and deployment configuration names that have been modified.

To view the full content of the usage information shared to PingCAP, set the TIUP_CLUSTER_DEBUG=enable environment variable when executing the TiUP command. For example:

TIUP_CLUSTER_DEBUG=enable tiup cluster list

Enable telemetry

To enable the TiUP telemetry collection, execute the following command:

tiup telemetry enable

Disable telemetry

To disable the TiUP telemetry collection, execute the following command:

tiup telemetry disable

Check telemetry status

For TiUP telemetry, execute the following command to check the telemetry status:

tiup telemetry status

Compliance

To meet compliance requirements in different countries or regions, the usage information is sent to servers located in different countries according to the IP address of the sender machine:

  • For IP addresses from the Chinese mainland, usage information is sent to and stored on cloud servers in the Chinese mainland.
  • For IP addresses from outside of the Chinese mainland, usage information is sent to and stored on cloud servers in the US.

See PingCAP Privacy Policy for details.

Was this page helpful?