+++ This bug was initially created as a clone of Bug #1427616 +++ Description of problem: Introduced in: https://issues.jboss.org/browse/HWKALERTS-214 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" {"currentNode":"hawkular-metrics-90tfy","distributed":"true","Implementation-Version":"0.23.6.Final","Built-From-Git-SHA1":"af57ffa0e3557ce5f50ef825d35322a0238c0f44","status":"STARTED","members":"hawkular-metrics-90tfy"} How reproducible: 100% 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.
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