[
https://issues.apache.org/jira/browse/METRON-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257418#comment-16257418
]
ASF GitHub Bot commented on METRON-1301:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/832
Spun this up on full dev, and saw that sorting worked as expected in the
UI. This worked both when no groupings were selected and also when drilling
down (e.g. grouping by ip_dst_addr and country).
I also like the refactorings a lot. It's good stuff that makes life easier
and more testable.
+1, assuming @cestella is happy with the changes you made on his comments.
> Alerts UI - Sorting on Triage Score Unexpectedly Filters Some Records
> ---------------------------------------------------------------------
>
> Key: METRON-1301
> URL: https://issues.apache.org/jira/browse/METRON-1301
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.4.1
> Reporter: Nick Allen
> Assignee: Nick Allen
> Fix For: Next + 1
>
> Attachments: 01-Alerts-UI-default-view.png, 02-Sort-on-Score-field.png
>
>
> Sorting on a field like threat triage score in the Alerts UI removes any
> records that do not have a threat triage score defined from the search
> results.
> For example, I have 7 records when sorted by timestamp. All 7 records have a
> timestamp field.
> After sorting by score (threat triage score) there are only 5 records. The 2
> records missing a threat triage score are no longer included.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
