TimescaleDB collects anonymous usage data to help us better understand and assist our users. It also helps us provide some services, such as automated version checking. Your privacy is the most important thing to us, so we do not collect any personally identifying information. In particular, the UUID (user ID) fields contain no identifying information, but are randomly generated by appropriately seeded random number generators.

This is an example of the JSON data file that is sent for a specific deployment:

If you want to see the exact JSON data file that is sent, use the get_telemetry_report API call.

Note

Telemetry reports are different if you are using an open source or community version of TimescaleDB. For these versions, the report includes an edition field, with a value of either apache_only or community.

If you want to adjust which metadata is included or excluded from the telemetry report, you can do so in the _timescaledb_catalog.metadata table. Metadata which has include_in_telemetry set to true, and a value of timescaledb_telemetry.cloud, is included in the telemetry report.

Telemetry reports are sent periodically in the background. In response to the telemetry report, the database receives the most recent version of TimescaleDB available for installation. This version is recorded in your server logs, along with any applicable out-of-date version warnings. You do not have to update immediately to the newest release, but we highly recommend that you do so, to take advantage of performance improvements and bug fixes.

It is highly recommend that you leave telemetry enabled, as it provides useful features for you, and helps to keep improving Timescale. However, you can turn off telemetry if you need to for a specific database, or for an entire instance.

Important

If you turn off telemetry, the version checking feature is also turned off.

  1. Open your PostgreSQL configuration file, and locate the timescaledb.telemetry_level parameter. See the PostgreSQL configuration file instructions for locating and opening the file.

  2. Change the parameter setting to off:

    timescaledb.telemetry_level=off
  3. Reload the configuration file:

    pg_ctl
  4. Alternatively, you can use this command at the psql prompt, as the root user:

    ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=off

    This command disables telemetry for the specified system, database, or user.

  1. Open your PostgreSQL configuration file, and locate the 'timescaledb.telemetry_level' parameter. See the PostgreSQL configuration file instructions for locating and opening the file.

  2. Change the parameter setting to 'off':

    timescaledb.telemetry_level=basic
  3. Reload the configuration file:

    pg_ctl
  4. Alternatively, you can use this command at the psql prompt, as the root user:

    ALTER [SYSTEM | DATABASE | USER] { *db_name* | *role_specification* } SET timescaledb.telemetry_level=basic

    This command enables telemetry for the specified system, database, or user.

Keywords

Found an issue on this page?

Report an issue!