​
Telemetry

Flipt developers rely on anonymous usage data to help prioritize new features and improve the product. The information collected is completely anonymous, never shared with external entities, and you can opt-out at any time.

The telemetry data is collected by default, but you can disable it by following the instructions below.

Telemetry is only collected when Flipt is running, once at startup and then every 4 hours.

​
What Kind of Data is Collected?

  • Flipt version (i.e.: v1.21.0)
  • Database backend (i.e.: Postgres)
  • Cache backend (i.e.: Redis)
  • Authentication methods (i.e.: OIDC)

We use Segment to collect the data. Only the Flipt team has access to the raw data.

Here is an example of the telemetry data sent to Segment:

{
  "version": "1.1",
  "uuid": "1545d8a8-7a66-4d8d-a158-0a1c576c68a6",
  "lastTimestamp": "2023-04-25T01:01:51Z",
  "flipt": {
    "version": "v1.21.1",
    "os": "linux",
    "arch": "amd64",
    "storage": {
      "database": "postgres",
      "cache": "redis"
    },
    "authentication": {
      "methods": "oidc"
    }
  }
}

You can always view the current schema of the telemetry data and see how it’s collected on GitHub.

​
How to Disable Telemetry

Telemetry collection can be disabled in several ways:

​
Configuration File

meta:
  telemetry_enabled: false

​
Environment Variables

export FLIPT_META_TELEMETRY_ENABLED=false

Telemetry can also be disabled by setting the DO_NOT_TRACK environment variable to true or 1:

export DO_NOT_TRACK=true

​
Telemetry

Flipt developers rely on anonymous usage data to help prioritize new features and improve the product. The information collected is completely anonymous, never shared with external entities, and you can opt-out at any time.

The telemetry data is collected by default, but you can disable it by following the instructions below.

Telemetry is only collected when Flipt is running, once at startup and then every 4 hours.

​
What Kind of Data is Collected?

  • Flipt version (i.e.: v1.21.0)
  • Database backend (i.e.: Postgres)
  • Cache backend (i.e.: Redis)
  • Authentication methods (i.e.: OIDC)

We use Segment to collect the data. Only the Flipt team has access to the raw data.

Here is an example of the telemetry data sent to Segment:

{
  "version": "1.1",
  "uuid": "1545d8a8-7a66-4d8d-a158-0a1c576c68a6",
  "lastTimestamp": "2023-04-25T01:01:51Z",
  "flipt": {
    "version": "v1.21.1",
    "os": "linux",
    "arch": "amd64",
    "storage": {
      "database": "postgres",
      "cache": "redis"
    },
    "authentication": {
      "methods": "oidc"
    }
  }
}

You can always view the current schema of the telemetry data and see how it’s collected on GitHub.

​
How to Disable Telemetry

Telemetry collection can be disabled in several ways:

​
Configuration File

meta:
  telemetry_enabled: false

​
Environment Variables

export FLIPT_META_TELEMETRY_ENABLED=false

Telemetry can also be disabled by setting the DO_NOT_TRACK environment variable to true or 1:

export DO_NOT_TRACK=true