Bug 1434785
Summary: | Include the tag query feature of hawkular-alerts | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Mooli Tayer <mtayer> |
Component: | Hawkular | Assignee: | Matt Wringe <mwringe> |
Status: | CLOSED ERRATA | QA Contact: | Liming Zhou <lizhou> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.5.1 | CC: | aos-bugs, eparis, jcantril, jshaughn, lponce, mwringe, penli, pweil, tdawson, wsun |
Target Milestone: | --- | ||
Target Release: | 3.5.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1427616 | Environment: | |
Last Closed: | 2017-05-18 09:27:31 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: | 1427616 | ||
Bug Blocks: |
Description
Mooli Tayer
2017-03-22 11:36:25 UTC
This feature is critical for the cm-ops effort. We relay on tags to figure out what are the alerts a specific ManageIQ already saw. With out this feature each poll we will get all alerts. We know to ignore those but we will overload network usage and have severe performance consequences. This fix for this is in image openshift3/metrics-hawkular-metrics:3.5.0-15 Perhaps you can reuse some curl-based scripts to create a simple trigger, push some metric and generate alerts. Then those alerts can be queried with the tagQuery feature which is discussed in the bugzilla. The JIRA https://issues.jboss.org/browse/HWKALERTS-210 is not related to this case but it has some scripting to help writting tests. They can be modified to have tags and check the tagQuery feature. 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:1235 |