Bug 1464981
| Summary: | [RFE]: Sanitized health check format | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | John Spray <john.spray> |
| Component: | RADOS | Assignee: | John Spray <john.spray> |
| Status: | CLOSED ERRATA | QA Contact: | shylesh <shmohan> |
| Severity: | urgent | Docs Contact: | Erin Donnelly <edonnell> |
| Priority: | urgent | ||
| Version: | 3.0 | CC: | anharris, ceph-eng-bugs, dzafman, edonnell, hnallurv, jdurgin, john.spray, kchai, kdreyer |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.1.4-1.el7cp Ubuntu: ceph_12.1.4-2redhat1xenial | Doc Type: | Enhancement |
| Doc Text: |
.Ceph health checks are more easily integrated with external alerting systems
Ceph's built-in health checks have been refactored to enable more robust integration with external alerting systems. For each condition that is checked, there is now a unique status code, for example `PG_AVAILABILITY`.
NOTE: Any external script that was relying on the JSON syntax of the `ceph status` or `ceph health` command output must be updated for the new format. To ease migration, set the `mon_health_preluminous_compat` parameter to `True` on Monitors to instruct `ceph status` and `ceph health` to generate old-style health output in addition to the new output.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-05 23:35:34 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
John Spray
2017-06-26 11:01:36 UTC
No work on this upstream yet. This is the health check changes that we landed last week. Yes, it's in there. Just bad housekeeping on my part: I've marked the upstream ticket resolved now. 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 |