Merge pull request #1929 from samalba/docs-cli-telemetry
docs: added a page about CLI telemetry
This commit is contained in:
commit
9f196ca14f
20
docs/core-concepts/1218-cli-telemetry.md
Normal file
20
docs/core-concepts/1218-cli-telemetry.md
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
slug: /1218/cli-telemetry
|
||||
displayed_sidebar: europa
|
||||
---
|
||||
|
||||
# CLI Telemetry
|
||||
|
||||
The dagger CLI implements telemetry that provides information about the usage from the Dagger Community. Although optional, this helps us to improve dagger by measuring the usage of the main features.
|
||||
|
||||
## What is tracked?
|
||||
|
||||
Command names are tracked along with the version of dagger and the platform it's running on. CLI telemetry events are anonymized for privacy purposes, they are not linked to a specific identity.
|
||||
|
||||
If you want to know more, you can check the telemetry implementation in dagger's source code.
|
||||
|
||||
## Can I disable the telemetry?
|
||||
|
||||
Dagger implements [the DNT (Console Do Not Track) standard](https://consoledonottrack.com/).
|
||||
|
||||
As a result, you can disable the telemetry by setting the environment variable `DO_NOT_TRACK=1` before running dagger.
|
@ -109,6 +109,7 @@ module.exports = {
|
||||
"core-concepts/container-images",
|
||||
"core-concepts/what-is-cue",
|
||||
"core-concepts/dagger-cue",
|
||||
"core-concepts/cli-telemetry",
|
||||
],
|
||||
},
|
||||
{
|
||||
|
Reference in New Issue
Block a user