惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Stack Overflow Blog
Stack Overflow Blog
S
SegmentFault 最新的问题
大猫的无限游戏
大猫的无限游戏
The GitHub Blog
The GitHub Blog
M
MIT News - Artificial intelligence
T
Tailwind CSS Blog
aimingoo的专栏
aimingoo的专栏
Last Week in AI
Last Week in AI
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
罗磊的独立博客
H
Help Net Security
Engineering at Meta
Engineering at Meta
Microsoft Security Blog
Microsoft Security Blog
阮一峰的网络日志
阮一峰的网络日志
J
Java Code Geeks
T
The Blog of Author Tim Ferriss
Hugging Face - Blog
Hugging Face - Blog
C
Check Point Blog
F
Fortinet All Blogs
腾讯CDC
博客园 - Franky
WordPress大学
WordPress大学
U
Unit 42

OneUptime Blog

How to Monitor Azure App Services (PaaS) with OpenTelemetry Grafana Stack vs OneUptime: DIY Observability or Unified Platform? Your AI Workloads Are About to Blow Up Your Observability Bill The Great Observability Consolidation Is Here How to Write Custom Object Classes for Ceph How to Write Custom Ceph Manager Modules How to Write a ceph.conf Configuration File How to Use Rook-Ceph with OpenShift How to Use Rook-Ceph with Longhorn for Comparison How to Configure Volume Snapshot Class for RBD in Rook How to Configure VolumeReplicationClass Scheduling Intervals in Rook How to Set Up Volume Replication with Rook-Ceph How to Create Volume Group Snapshots with Rook CSI How to Visualize Ceph Network Performance in Grafana How to Enable Virtual Host-Style Bucket Access in Rook How to View Runtime Configuration via Admin Socket How to View Quota Settings and Update Stats in Ceph RGW How to View PG Scaling Recommendations with autoscale-status How to View PG Distribution via Admin Socket How to View Performance Metrics in the Ceph Dashboard How to View OSD Performance Counters in Ceph How to View Connection Status via Admin Socket How to View Ceph Cluster Summary Dashboard via CLI How to Version Control Rook-Ceph Configuration How to Version Control Ceph Infrastructure with Terraform How to Verify Kubernetes Node Requirements for Rook-Ceph Deployment How to Verify Health Before and After Rook Upgrades How to Verify Data Integrity with Deep Scrubbing How to Verify Complete Rook-Ceph Cleanup How to Verify Backup Integrity from Ceph Snapshots
How to Understand What Data Ceph Telemetry Collects
Nawaz Dhandala · 2026-03-31 · via OneUptime Blog

Overview of Telemetry Data Categories

Ceph telemetry collects data in distinct channels. Each channel covers a specific category of information. Before opting in, you can preview each channel's payload to understand what is shared.

Preview all telemetry data:

ceph telemetry show

Preview a specific channel:

ceph telemetry show basic
ceph telemetry show crash
ceph telemetry show device

Basic Channel - What Is Collected

The basic channel includes anonymized cluster topology and configuration:

  • Ceph version and release
  • Number of monitors, OSDs, and MDSs
  • OSD and pool configurations (without hostnames or IPs)
  • Cluster ID (a UUID, not tied to any personally identifiable information)
  • Enabled features and flags
  • CRUSH map structure (anonymized)

Example of basic telemetry output:

ceph telemetry show basic | python3 -m json.tool | head -50

Crash Channel - What Is Collected

The crash channel sends anonymized crash reports:

  • Crash timestamp and Ceph version
  • Stack trace from the crash
  • Daemon type (OSD, MON, MGR) that crashed
  • No hostname, IP address, or cluster-specific data

View current crash reports:

ceph crash ls
ceph crash info <crash-id>

Device Channel - What Is Collected

The device channel shares SMART health data predictions:

  • Drive model and firmware version
  • SMART attributes used for health scoring
  • Predicted failure probability
  • No serial numbers or host associations

Check device health data:

ceph device ls
ceph device info <device-id>

What Is NOT Collected

Ceph telemetry explicitly excludes:

  • Hostnames and IP addresses
  • Object names, bucket names, or user data
  • Ceph user account names
  • RGW, CephFS, or RBD client data
  • Any data stored in the cluster

Inspecting the Full Telemetry Report

Generate the complete JSON report that would be sent:

ceph telemetry show --format json > /tmp/telemetry-preview.json
cat /tmp/telemetry-preview.json | python3 -m json.tool | less

Count items by section:

ceph telemetry show --format json | python3 -c "
import sys, json
d = json.load(sys.stdin)
for k, v in d.items():
    print(f'{k}: {type(v).__name__}')
"

Rook Toolbox Commands

Access telemetry inspection from the toolbox:

kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- \
  ceph telemetry show basic

Summary

Ceph telemetry collects only anonymized cluster structure and health data - no user data, hostnames, or personally identifiable information is ever sent. The basic, crash, and device channels each cover distinct aspects of cluster metadata. Running ceph telemetry show before opting in lets you verify the payload is acceptable for your organization's data policies.