Skip to content

Telemetry

Alexey Zilber edited this page Apr 30, 2022 · 5 revisions

Telemetry Principles

Telemetry can be a valuable way of understanding and tailoring our products to better meet your needs. It gives us some insight into which features are being used, so that we have a better understanding of where to invest our efforts going forward.

The below defines our principles on how we collect and use telemetry data. We have only implemented telemetry into the open source version to date, and so the below applies to this version only.

Privacy

We do not automatically collect any personally identifiable information. We do not collect IP addresses.

We collect at most, the following points of information:

  1. BuildId
  2. sysDate
  3. sysType
  4. geoipType
  5. geoipFmt
  6. os
  7. vmSys
  8. Inode

Not all points are available on every OS nor every interaction. Telemetry may be easily disabled by using the -l (or --dont-use-telemetry) runtime flag.

Transparency

The telemetry package is open source; you have the ability to inspect the code, understand to which ConsulTent endpoint we are sending the data, and what we are capturing at all times. Any changes to the telemetry will be highlighted in the release notes. You can subscribe to updates by watching the ConsulTent/geoip2redis repo on github.

Control

Telemetry in the our software is opt-out. We will always be transparent about where telemetry has been added and provide documentation on how to disable it.

Minimalism

We only ever collect what is required at any given point in time. We do not pre-empt future requirements, or collect anything ‘just in case’.