Discussion on the Usage Scenarios of tiup telemetry

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tiup telemetry 使用场景讨论

| username: TiDBer_JUi6UvZm

Refer to here tiup telemetry | PingCAP 文档中心

When TiUP telemetry is enabled, executing TiUP commands will share usage information with PingCAP, including (but not limited to):

  • Randomly generated telemetry identifier
  • Execution status of TiUP commands, such as whether the command was successful, command execution time, etc.
  • Deployment details using TiUP, such as hardware information of the target machine, component version numbers, modified deployment configuration names, etc.

The following information will not be shared:

  • Exact names of the clusters
  • Cluster topology
  • Cluster configuration files

TiUP uses the command tiup telemetry to control telemetry.

Is this considered a backdoor? In actual usage scenarios, do you disable this feature? Is it allowed in banks?

| username: ShawnYan | Original post link

It is currently disabled by default.

| username: stephanie | Original post link

We will not enable this feature during use.

| username: 小龙虾爱大龙虾 | Original post link

Can the bank’s database access the external network?

| username: Daniel-W | Original post link

It is closed, and they are all internal networks. Even if information is collected, it cannot be sent out.

| username: Kamner | Original post link

In TiUP version v1.11.3 and above, the telemetry feature is disabled by default.

Generally, database servers are placed in an internal network and cannot access the external network.

| username: 这里介绍不了我 | Original post link

Have you enabled this feature yet?

| username: Miracle | Original post link

I’m a bit curious why this feature was designed in the first place.

| username: DBAER | Original post link

This feature works, I just discovered it.

| username: cassblanca | Original post link

How could a bank’s database be exposed to the public network? They are all isolated in different DMZs. Even if this feature is enabled, it shouldn’t have much impact.

| username: TiDBer_JUi6UvZm | Original post link

“In TiUP versions v1.11.3 and above, the telemetry feature is disabled by default, meaning usage information is not collected and shared with PingCAP by default. In TiUP versions below v1.11.3, the telemetry feature is enabled by default, meaning usage information is collected and shared with PingCAP by default to improve the product.”

TiDB is quite bold in its product design. Kudos to them, and I quietly and proactively disable this feature (even though it is now disabled by default).

| username: TiDBer_JUi6UvZm | Original post link

They are also disabled by default. It’s unknown.

| username: TiDBer_JUi6UvZm | Original post link

Although it can’t, it also shouldn’t capture data. The official later changed it to be disabled by default, which should also be considered a risk.

| username: wangkk2024 | Original post link

Here to learn.

| username: tidb狂热爱好者 | Original post link

These are just metrics for CPU and memory usage, not business data. Moreover, it has been shut down with the purpose of better designing the database. It aims to help community residents analyze issues for free. The reason for shutting it down is the concern that too much database content might be leaked and could be exploited by commercial competitors.

| username: 友利奈绪 | Original post link

It’s better not to enable it.

| username: TiDBer_BeWd6Ihe | Original post link

Hahaha,

| username: zhaokede | Original post link

Generally, servers are within an internal network and cannot send data to the public network; telemetry is disabled by default.

| username: zhaokede | Original post link

In a strictly managed data center with firewall whitelists and blacklists, uncontrolled data cannot be sent out.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.