You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by "Justin Leet (JIRA)" <ji...@apache.org> on 2018/06/20 14:39:00 UTC

[jira] [Commented] (METRON-1600) Solr should be using threat.triage.score everywhere instead of threat:triage:score (back end)

    [ https://issues.apache.org/jira/browse/METRON-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518205#comment-16518205 ] 

Justin Leet commented on METRON-1600:
-------------------------------------

[~rmerriman] Is this ticket covered by [https://github.com/apache/metron/pull/1055]? Can we just close this ticket?

> Solr should be using threat.triage.score everywhere instead of threat:triage:score (back end)
> ---------------------------------------------------------------------------------------------
>
>                 Key: METRON-1600
>                 URL: https://issues.apache.org/jira/browse/METRON-1600
>             Project: Metron
>          Issue Type: Sub-task
>            Reporter: Ryan Merriman
>            Priority: Major
>
> See [https://github.com/apache/metron/blob/feature/METRON-1416-upgrade-solr/metron-interface/metron-alerts/src/app/utils/constants.ts#L30]
> This results in alerts in the UI with valid threat.triage.score (e.g. a Snort alert with score 10) having a "-" for score.
> We should make sure this doesn't happen elsewhere throughout the code (e.g. metaalerts aggregates things by threat:triage:score, but there is a variable for it, but we should check anyway).
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)