Hi Artur,
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.

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"?

Open to ideas. Also, there is [HWKALERTS-62: Allow any data to store contextual information] which could also come into play.

On 7/13/2015 4:58 AM, Artur Dryomov wrote:

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].