6 The telemetry module sends anonymous data about the cluster back to the Ceph
7 developers to help understand how Ceph is used and what problems users may
10 Reported telemetry includes:
12 * capacity of the cluster
13 * number of monitors, managers, OSDs, MDSs, radosgws, or other daemons
14 * software version currently being used
15 * number and types of RADOS pools and CephFS file systems
16 * information about daemon crashes, including
19 - version of the daemon
20 - operating system (OS distribution, kernel version)
21 - stack trace identifying where in the Ceph code the crash occurred
23 The data being reported does *not* contain any sensitive
24 data like pool names, object names, object contents, or hostnames.
26 It contains counters and statistics on how the cluster has been
27 deployed, the version of Ceph, the distribition of the hosts and other
28 parameters which help the project to gain a better understanding of
31 Data is sent over HTTPS to *telemetry.ceph.com*.
36 You can look at what data is reported at any time with the command::
38 ceph mgr module enable telemetry
41 If you have any concerns about privacy with regard to the information included in
42 this report, please contact the Ceph developers.
47 The *telemetry* module is enabled with::
49 ceph mgr module enable telemetry
52 Telemetry can be disabled with::
59 The module compiles and sends a new report every 72 hours by default.
60 You can adjust this interval with::
62 ceph config set mgr mgr/telemetry/interval 24 # report every day
64 Contact and Description
65 -----------------------
67 A contact and description can be added to the report. This is completely optional.::
69 ceph config set mgr mgr/telemetry/contact 'John Doe <john.doe@example.com>'
70 ceph config set mgr mgr/telemetry/description 'My first Ceph cluster'
75 The report is sent in JSON format, and can be printed::
79 So you can inspect the content if you have privacy concerns.