Can telemetry be completely disabled in version 6.1.1?

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

Original topic: 6.1.1遥测是否可以彻底关闭

| username: army

[TiDB Usage Environment] Production Environment / Testing / Poc
Production Environment
[TiDB Version]
v6.1.1
[Reproduction Path] What operations were performed to cause the issue
Here are the steps I followed according to the documentation 遥测 | PingCAP 文档中心 to disable telemetry:

  1. Modify pd’s dashboard.enable-telemetry: false and restart pd
  2. Modify the instance’s global variable SET GLOBAL tidb_enable_telemetry = 0;
  3. Disable tiup telemetry with tiup telemetry disable
  4. Restart the entire cluster

However, after restarting, I still found telemetry data being sent when logging into the dashboard interface, including internal network URLs, etc. Is there a way to completely disable it?
[Encountered Issue: Issue Phenomenon and Impact]

[Resource Configuration] Enter TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

| username: 裤衩儿飞上天 | Original post link

Changing only this parameter is not enough; you also need to disable TiUP and the dashboard telemetry.
Reference: Telemetry | PingCAP Documentation Center

| username: army | Original post link

Step 1: The PD properties modified through tiup cluster edit-config still send a small amount of information after restarting the cluster, even though TiUP has been shut down.

| username: 裤衩儿飞上天 | Original post link

The image is not visible. Please provide the text you need translated.

| username: tidb菜鸟一只 | Original post link

Use tiup cluster edit-config to modify the cluster configuration:

server_configs:
  tidb:
    enable-telemetry: false

Add this as well.

Additionally, you can use SHOW config WHERE NAME LIKE '%telemetry%' to check if all telemetry settings are false. It seems that even after disabling it, it still shows true…

| username: army | Original post link

The “show config” command shows that both TiDB and PD are turned off, but there are still transmissions.

| username: ShawnYan | Original post link

Will only the current cluster’s PD send it?

| username: 裤衩儿飞上天 | Original post link

Sorry, I didn’t review the topic carefully yesterday.

| username: sladenew | Original post link

It seems to be caused by SENTRY. You need to set the SENTRY dsn to empty.

| username: system | Original post link

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