Bug 1434785

Summary: Include the tag query feature of hawkular-alerts
Product: OpenShift Container Platform Reporter: Mooli Tayer <mtayer>
Component: HawkularAssignee: Matt Wringe <mwringe>
Status: CLOSED ERRATA QA Contact: Liming Zhou <lizhou>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.1CC: aos-bugs, eparis, jcantril, jshaughn, lponce, mwringe, penli, pweil, tdawson, wsun
Target Milestone: ---   
Target Release: 3.5.z   
Hardware: Unspecified   
OS: Unspecified   
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:
Bug Depends On: 1427616    
Bug Blocks:    

Description Mooli Tayer 2017-03-22 11:36:25 UTC
+++ This bug was initially created as a clone of Bug #1427616 +++

Description of problem:
Introduced in:

Version-Release number of selected component (if applicable):

# oc version
oc v1.4.0-alpha.1+5f9a5ec-217
kubernetes v1.4.0+776c994
features: Basic-Auth GSSAPI Kerberos SPNEGO

# curl -k -s     -H "Hawkular-Tenant: $HAWKULAR_TENANT"     -H "Authorization: Bearer $HAWKULAR_TOKEN"      "https://$HAWKULAR_HOST/hawkular/alerts/status"


How reproducible:

events?tags=type queries work but a event?tagQuery is ignored.

BTW IT would be nice if hawkular would alert on query param it does not know but that is beside the point

--- Additional comment from Matt Wringe on 2017-02-28 13:47:46 EST ---

https://issues.jboss.org/browse/HWKALERTS-214 is not in any released Hawkular Alerts version. Once Alerts is released, Hawkular Metrics will be updated to include this new version.

Once availabe, origin metrics will be updated to include the newer version of Hawkular Metrics which will include this alerts feature.

Comment 1 Mooli Tayer 2017-03-22 11:46:20 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.

Comment 9 Troy Dawson 2017-04-28 15:55:34 UTC
This fix for this is in image

Comment 18 Lucas Ponce 2017-05-03 10:16:38 UTC
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.

Comment 26 errata-xmlrpc 2017-05-18 09:27:31 UTC
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.