Gary Brown created RTGOV-154:
--------------------------------
Summary: Situation list filter
Key: RTGOV-154
URL:
https://issues.jboss.org/browse/RTGOV-154
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
Situation events are created when an event processor detects a problem based on activity
information generated by executing business transactions.
The situations are associated with a target component that indicates where the problem has
arisen. In some situations, a particular component may be known to an administrator, and
therefore they wish to temporarily ignore any problems being reported about it.
Although this filtering could be provided in the presentation layer, it may be better that
it is centrally managed, to enable other applications that access the Situations list
through the REST API to also be subject to the same filtering.
The issue is where to apply this filter, and where will it get the list of blacklisted
entries from. In terms of the filter, should the overall list remain unchanged, and just
have a derived list that applies the filter?
If the complete list is maintained, then the benefit is that when the component is removed
from the blacklist, its associated Situations would then immediately re-appear within the
displayed list.
The other point to consider is whether Situations associated blacklisted components should
be persisted, or atleast marked to indicate that they were flagged as a known problem?
As this mechanism is primarily intended to de-clutter the UI, to avoid known problems
overshadowing other Situations that may occur, it is likely that persisting Situation
events would be unaffected by this mechanism.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira