--- title: "Ceph integration | Grafana Cloud documentation" description: "Learn about Ceph Grafana Cloud integration." --- > For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt). # Ceph integration for Grafana Cloud Ceph uniquely delivers object, block, and file storage in one unified system. This integration includes 6 useful alerts and 1 pre-built dashboard to help monitor and visualize Ceph metrics. ## Before you begin In order for the Ceph integration to work, you must enable the built-in Prometheus plugin in your Ceph cluster, with the provided command: ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```none ceph mgr module enable prometheus ``` ## Install Ceph integration for Grafana Cloud 1. In your Grafana Cloud stack, click **Connections** in the left-hand menu. 2. Find **Ceph** and click its tile to open the integration. 3. Review the prerequisites in the **Configuration Details** tab and set up Grafana Alloy to send Ceph metrics to your Grafana Cloud instance. 4. Click **Install** to add this integration’s pre-built dashboard and alerts to your Grafana Cloud instance, and you can start monitoring your Ceph setup. ## Configuration snippets for Grafana Alloy ### Simple mode These snippets are configured to scrape a single Ceph instance running locally with default ports. First, **manually** copy and append the following snippets into your alloy configuration file. ### Metrics snippets Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy discovery.relabel "metrics_integrations_integrations_ceph" { targets = [{ __address__ = "cephnode1:9283", ceph_cluster = "my-cluster", }] rule { target_label = "instance" replacement = constants.hostname } } prometheus.scrape "metrics_integrations_integrations_ceph" { targets = discovery.relabel.metrics_integrations_integrations_ceph.output forward_to = [prometheus.remote_write.metrics_service.receiver] job_name = "integrations/ceph" } ``` ### Advanced mode The following snippets provide examples to guide you through the configuration process. To instruct Grafana Alloy to scrape your Ceph instances, **manually** copy and append the snippets to your alloy configuration file, then follow subsequent instructions. ### Advanced metrics snippets Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```alloy discovery.relabel "metrics_integrations_integrations_ceph" { targets = [{ __address__ = "cephnode1:9283", ceph_cluster = "my-cluster", }] rule { target_label = "instance" replacement = constants.hostname } } prometheus.scrape "metrics_integrations_integrations_ceph" { targets = discovery.relabel.metrics_integrations_integrations_ceph.output forward_to = [prometheus.remote_write.metrics_service.receiver] job_name = "integrations/ceph" } ``` To monitor your Ceph instance, you must use a [discovery.relabel](/docs/alloy/latest/reference/components/discovery.relabel/) component to discover your Ceph Prometheus endpoint and apply appropriate labels, followed by a [prometheus.scrape](/docs/alloy/latest/reference/components/prometheus.scrape) component to scrape it. Configure the following properties within each `discovery.relabel` component: - `__address__`: The address to your Ceph Prometheus metrics endpoint. - `instance` label: `constants.hostname` sets the `instance` label to your Grafana Alloy server hostname. If that is not suitable, change it to a value uniquely identifies this Ceph instance. - `ceph_cluster`: must be the value that identifies the Ceph cluster this instance belongs to. If you have multiple Ceph servers to scrape, configure one `discovery.relabel` for each and scrape them by including each under `targets` within the `prometheus.scrape` component. ## Dashboards The Ceph integration installs the following dashboards in your Grafana Cloud instance to help monitor your system. - Ceph - Cluster **Ceph Cluster** ## Alerts The Ceph integration includes the following useful alerts: Expand table | Alert | Description | |------------------------|-----------------------------------------------------------------| | CephUnhealthyWarning | Warning: The Ceph cluster has warning level issues. | | CephUnhealthyCritical | Critical: The Ceph cluster has critical issues. | | CephDiskLessThan15Left | Warning: The Ceph cluster has less than 15% storage space left. | | CephDiskLessThan5Left | Critical: The Ceph cluster has less than 5% storage space left. | | OSDNodeDown | Warning: The OSD node is down. | | MDSDown | Warning: All MDS nodes down. | ## Metrics The most important metrics provided by the Ceph integration, which are used on the pre-built dashboard and Prometheus alerts, are as follows: - ceph\_bluestore\_commit\_lat\_count - ceph\_cluster\_total\_bytes - ceph\_cluster\_total\_used\_bytes - ceph\_filestore\_journal\_latency\_count - ceph\_health\_status - ceph\_mds\_metadata - ceph\_mon\_metadata - ceph\_mon\_num\_sessions - ceph\_mon\_quorum\_status - ceph\_osd\_apply\_latency\_ms - ceph\_osd\_commit\_latency\_ms - ceph\_osd\_in - ceph\_osd\_metadata - ceph\_osd\_numpg - ceph\_osd\_op\_r - ceph\_osd\_op\_r\_latency\_count - ceph\_osd\_op\_r\_latency\_sum - ceph\_osd\_op\_r\_out\_bytes - ceph\_osd\_op\_w - ceph\_osd\_op\_w\_in\_bytes - ceph\_osd\_op\_w\_latency\_count - ceph\_osd\_op\_w\_latency\_sum - ceph\_osd\_recovery\_ops - ceph\_osd\_up - ceph\_pg\_active - ceph\_pg\_backfill - ceph\_pg\_backfill\_toofull - ceph\_pg\_clean - ceph\_pg\_creating - ceph\_pg\_deep - ceph\_pg\_degraded - ceph\_pg\_down - ceph\_pg\_forced\_backfill - ceph\_pg\_forced\_recovery - ceph\_pg\_incomplete - ceph\_pg\_inconsistent - ceph\_pg\_peered - ceph\_pg\_peering - ceph\_pg\_recovering - ceph\_pg\_remapped - ceph\_pg\_repair - ceph\_pg\_scrubbing - ceph\_pg\_stale - ceph\_pg\_undersized - ceph\_pg\_wait\_backfill - ceph\_pool\_metadata - ceph\_pool\_num\_bytes\_recovered - ceph\_pool\_num\_objects\_recovered - ceph\_pool\_objects - ceph\_pool\_quota\_bytes - ceph\_pool\_quota\_objects - ceph\_rgw\_metadata - ceph\_unclean\_pgs - up ## Changelog md ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```md # 1.0.1 - November 2024 * Update mixin: - Adjust stat panels to support light theme # 1.0.0 - February 2024 * Updated mixin: - Replace all Angular panels with React based panels. - Address lint issues # 0.0.6 - September 2023 * Update Grafana Agent configuration snippets to include filtered metrics used in gauge panels # 0.0.5 - September 2023 * New Filter Metrics option for configuring the Grafana Agent, which saves on metrics cost by dropping any metric not used by this integration. Beware that anything custom built using metrics that are not on the snippet will stop working. * New hostname relabel option, which applies the instance name you write on the text box to the Grafana Agent configuration snippets, making it easier and less error prone to configure this mandatory label. # 0.0.4 - September 2022 * Update panels descriptions. # 0.0.3 - April 2022 * Update mixin to latest version: - Removes all cluster variable in favor of `ceph_cluster` - Removes `node_exporter` based panels - Migrates from graph panel to time series panels - Removes panel stacking - Fixes `CephUnhealthy` alert - spliting into 2 different alerts with Warning and Critical levels - Sets default time threshold to 5m on all alerts # 0.0.2 - October 2021 * Update all rate queries to use `$__rate_interval`, so they respect the default resolution # 0.0.1 - August 2021 * Initial release ``` ## Cost By connecting your Ceph instance to Grafana Cloud, you might incur charges. To view information on the number of active series that your Grafana Cloud account uses for metrics included in each Cloud tier, see [Active series and dpm usage](/docs/grafana-cloud/fundamentals/active-series-and-dpm/) and [Cloud tier pricing](/products/cloud/pricing/).