Bug 1475982
| Summary: | Package cephmetrics | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Boris Ranto <branto> |
| Component: | Distribution | Assignee: | Boris Ranto <branto> |
| Status: | CLOSED ERRATA | QA Contact: | Lubos Trilety <ltrilety> |
| Severity: | medium | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | unspecified | ||
| Version: | 3.0 | CC: | branto, gmeno, hnallurv, john.spray, kdreyer, nlevine, pcuzner, vakulkar |
| Target Milestone: | rc | ||
| Target Release: | 3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cephmetrics-1.0-0.el7cp | Doc Type: | Enhancement |
| Doc Text: |
.Support for the Red Hat Ceph Storage Dashboard
The Red Hat Ceph Storage Dashboard provides a monitoring dashboard for Ceph clusters to visualize the cluster state. The dashboard is accessible from a web browser and provides a number of metrics and graphs about the state of the cluster, Monitors, OSDs, Pools, or network.
For details, see the link:https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/administration_guide/#monitoring-ceph-clusters-with-the-red-hat-ceph-storage-dashboard[Monitoring Ceph Clusters with Red Hat Ceph Storage Dashboard] section in the Administration Guide for Red{nbsp}Hat Ceph Storage 3.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-05 23:38:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1494421 | ||
|
Description
Boris Ranto
2017-07-27 17:08:45 UTC
There's a cephmetrics build in Ceph 3.0 errata which contains cephmetrics packages. Prometheus is not shipped yet, cephmetrics for Ceph 3.0 uses graphite. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3387 |