How to disable InfluxDB 3 Core usage telemetry

Disabling InfluxDB 3 Core usage telemetry opts a server out of hourly usage-data uploads to InfluxData. This matters on restricted, regulated, or offline hosts where outbound product telemetry must be disabled before the database service is treated as compliant.

InfluxDB 3 Core exposes the opt-out through the disable-telemetry-upload configuration option and the matching startup flag. For a packaged Linux service, saving the option in /etc/influxdb3/influxdb3-core.conf keeps the setting persistent through the package launcher.

The server can still log local telemetry-store initialization during startup, so do not use that line as proof of failure. Confirm the saved configuration entry, restart the influxdb3-core service, and check the local health endpoint after the service returns.

1. Inspect the loaded InfluxDB 3 Core service and config path.

   $ systemctl cat influxdb3-core
   # /usr/lib/systemd/system/influxdb3-core.service
   [Service]
   User=influxdb3
   Group=influxdb3
   ##### snipped #####

   Review any files shown under /etc/systemd/system/influxdb3-core.service.d/ before adding another override so local startup policy stays visible.

2. Back up the packaged TOML configuration file.

   $ sudo cp -a /etc/influxdb3/influxdb3-core.conf \
     /etc/influxdb3/influxdb3-core.conf.bak

3. Open the TOML configuration file in a privileged editor.

   $ sudoedit /etc/influxdb3/influxdb3-core.conf

   Related: How to configure InfluxDB 3 Core for systemd

4. Set the telemetry upload option in the TOML file.

   disable-telemetry-upload=true

   For a manual influxdb3 serve command, use --disable-telemetry-upload at startup. For Docker, pass the documented telemetry-disable environment variable when recreating the container.
   Related: How to run InfluxDB 3 Core with Docker

5. Confirm the saved configuration entry.

   $ sudo grep disable-telemetry-upload /etc/influxdb3/influxdb3-core.conf
   disable-telemetry-upload=true

6. Restart InfluxDB 3 Core so the new configuration is used.

   $ sudo systemctl restart influxdb3-core

   A restart interrupts writes and queries while the process stops and starts. Use a maintenance window when clients cannot safely retry.

   Related: How to manage the InfluxDB 3 Core service with systemctl

7. Confirm the service returned to active state after the restart.

   $ systemctl is-active influxdb3-core
   active

8. Check the local health endpoint with an authorized token.

   $ curl --silent http://127.0.0.1:8181/health \
     --header "Authorization: Bearer INFLUX_TOKEN"
   OK

   Replace INFLUX_TOKEN with an admin or monitoring token. A successful health response confirms the restarted service is answering after the telemetry opt-out was applied.
   Related: How to check InfluxDB server health
   Related: How to create an InfluxDB 3 Core admin token