[
https://issues.apache.org/jira/browse/METRON-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215863#comment-16215863
]
ASF GitHub Bot commented on METRON-1272:
----------------------------------------
Github user james-sirota commented on the issue:
https://github.com/apache/metron/pull/811
@nickwallen to avoid scope creep on this PR I created a follow-on PR to
figure out how to represent meta alerts in the facet panel.
https://issues.apache.org/jira/browse/METRON-1276
I agreee with @merrimanr that meta alerts contains multiple alerts each
with with distinct meta data and faceting them with the non-grouped alerts
doesn't make sense IMO. We do need to figure out a way to visualize metadata
of the meta alert (maybe have a separate facet panel for meta alerts?), but I
think this will add scope to this PR and therefore should be resolved outside
of this PR.
> Hide child alerts from searches and grouping if they belong to meta alerts
> --------------------------------------------------------------------------
>
> Key: METRON-1272
> URL: https://issues.apache.org/jira/browse/METRON-1272
> Project: Metron
> Issue Type: Improvement
> Reporter: Justin Leet
> Assignee: Justin Leet
>
> If an alert is already grouped into a meta alert, it's nice to route
> everything through the same query structure and allow sorting alongside them,
> etc. However, showing alerts that are already contained in a meta alert is
> potential clutter for a user and gives the impression an event has occurred
> twice if it's in a standalone alert and a metaalert.
> This should hide alerts contained in a meta alert from searches (which will
> always match the enclosing meta alert anyway, so nothing will be lost from
> the search).
> They should also be hidden from grouping calls, because the user has already
> manually grouped them during prior slicing and dicing.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
