<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Hi Artur,<br>
At the alerting level the main ability to categorize, outside of
playing games with trigger names and things like that, is provided
by Tags. Tags can be applied to Triggers and are basically
[category],name. You can then query Triggers via tags, and also
query alerts via the tags on their owning triggers.<br>
<br>
Because alerts have no inventory context, meaning it does not know
about resources, higher level API for tying together
Resources/Triggers/Alerts would need to be provided at the Hawkular
level. And that is fine, I think. So the questions become, "what
would a helpful API look like" and "where do we keep the
relationships, in alert tags, resource relationships,. etc"?<br>
<br>
Open to ideas. Also, there is [HWKALERTS-62: Allow any data to
store contextual information] which could also come into play.<br>
<br>
<div class="moz-cite-prefix">On 7/13/2015 4:58 AM, Artur Dryomov
wrote:<br>
</div>
<blockquote
cite="mid:CAC6O=UVbvG0sFgTLLGToMHFHuO2QRSCCDquX151aL6sDXFkKbA@mail.gmail.com"
type="cite">
<div dir="ltr"><span style="font-size:12.8000001907349px"></span>
<div style="font-size:12.8000001907349px">
<div style="font-size:12.8000001907349px">
<ul>
<li><span style="font-size:12.8000001907349px">Navigation.
I am not entirely sure that the current navigation
handles everything properly. For example, at the
moment all alerts are shown when browsing alerts.
There should be some categorization based on
resources, but at moment there are no proper API calls
supporting it. The only thing we have is filtering via
trigger IDs. Web UI solution is mostly a hack from my
perspective [4].</span><br>
</li>
</ul>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>