Telemetry Collected by InfluxDB 2.x

InfluxData collects information about the usage of InfluxDB. This “phone home” capability is intended to provide us with information about the broad user community and an understanding of how the platform is being used. These statistics are never shared with anyone else and help us make better decisions about product features, supportability, and more. Ultimately, sharing these metrics with us can help us better understand how you use our product and can help us improve the product over time.

Some people may feel uncomfortable about such telemetry data being gathered, so we want to be as transparent as possible about the information being captured and about how to ‘opt-out’, if you so choose.

Disabling Telemetry

Telemetry reporting is enabled by default. However, we’ve made it as easy as possible to ‘opt-out’ of the reporting. Simply start the InfluxDB process with the --reporting-disabled flag.

You can see the specific command in our documentation.

Metrics Collection

For each InfluxDB 2.x installation, we collect the following at startup and then every 8 hours:

archMicroarchitecture InfluxDB was compiled for
build dateDate associated with the InfluxDB build
commitSHA of commit associated with the InfluxDB build
cpusNumber of CPUs running InfluxDB
functionsFlux functions
idSnowflake identifier for the InfluxDB instance
Index partitionIdentifies the index partition used by the underlying InfluxDB storage engine
ipIP Address of the inbound connection which reports the statistics. This is not the specific IP Address of the machine running InfluxDB unless it is exposed directly on the public Internet.
orgIdentifier for an organization. Allows for grouping of statistics by organization within the InfluxDB instance
osOperating System InfluxDB is running on
resultText allowing grouping of Flux query invocations results
series file partitionIdentifies the series files in use for the underlying InfluxDB storage engine. This is not the metadata about series.
statusStatus of write ahead log (associated to number of successful /failed writes)
user_agentTypically, this is set by the browser, InfluxDB client libraries (includes the language [Go, JavaScript, Java, C#, Ruby, Python, etc.] and version), and other technologies [such as third-party dashboarding applications, etc.].
versionInfluxDB version

With those tag elements, we then leverage a combination of the unique combination of id, ip, and storage system specifics (where applicable) to capture usage counts of the various subsystems within InfluxDB.

buckets total counterTotal number of buckets present within the InfluxDB instance
bytes written counterTotal number of bytes written
bytes scanned counterTotal number of bytes scanned within the storage system via queries and tasks
dashboards total counterTotal number of dashboards present within the InfluxDB instance
flux function total counterTotal number of calls by function invoked within Flux
http api requests counterTotal number of API invocations by each API path
query duration histogramHistogram counting duration of queries into bins
organizations total counterTotal number of organizations present within the InfluxDB instance
scrapers total counterTotal number of scrapers configured within the InfluxDB instance
series total counterTotal number of series present within the InfluxDB instance
storage total counterTotal number of bytes stored within the InfluxDB instance
task scheduler gaugeNumber of tasks running within the InfluxDB instance
telegrafs total counterTotal number of telegraf configurations within the InfluxDB instance
tokens total counterTotal number of tokens present within the InfluxDB instance
uptime gaugeNumber of seconds InfluxDB has been continuously running
users total counterTotal number of users present within the InfluxDB instance
wal current segment gaugeNumber of bytes in the current segments for the write ahead log
wal writes total counterTotal number of writes to the write ahead log by status (ok, fail, etc.)
Scroll to Top