Bug 1427616 - Include the tag query feature in openshift origin
Summary: Include the tag query feature in openshift origin
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Hawkular
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Matt Wringe
QA Contact: Peng Li
URL:
Whiteboard:
Depends On:
Blocks: 1434785
TreeView+ depends on / blocked
 
Reported: 2017-02-28 17:54 UTC by Mooli Tayer
Modified: 2018-07-26 19:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1434785 (view as bug list)
Environment:
Last Closed: 2017-02-28 18:48:30 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Mooli Tayer 2017-02-28 17:54:26 UTC
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

Comment 1 Matt Wringe 2017-02-28 18:47:46 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.