Bug 1663289
Summary: | [Ceph-Dashboard] [No Data] Overall Ceph Health alert due to Prometheus scrape timeout | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | jquinn <jquinn> |
Component: | Ceph-Metrics | Assignee: | Boris Ranto <branto> |
Status: | CLOSED ERRATA | QA Contact: | Uday kurundwade <ukurundw> |
Severity: | high | Docs Contact: | Erin Donnelly <edonnell> |
Priority: | high | ||
Version: | 3.1 | CC: | branto, ceph-eng-bugs, edonnell, gmeno, hklein, mkasturi, mmuench, tserlin, ukurundw |
Target Milestone: | z1 | ||
Target Release: | 3.3 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | cephmetrics-2.0.7-1.el7cp | Doc Type: | Bug Fix |
Doc Text: |
.`No data` alerts are no longer generated
The {product} Dashboard generated a `No data` alert when a query returns no data. Previously, this alert sent an email to the administrator whenever there was a network outage or a node was down for maintenance. With this update, these `No data` alert are no longer generated.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-22 13:29:00 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: | 1726135 |
Comment 4
Giridhar Ramaraju
2019-08-05 13:09:42 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Upstream PR: https://github.com/ceph/cephmetrics/pull/243 Hi, Not getting any silent alert mails with "No data" after disabling prometheus module. Moving this BZ to verified state. 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-2019:3173 |