[jira] [Commented] (METRON-1216) ALERT-UI should not hard code sensor indices

["Ryan Merriman (JIRA)" <ji...@apache.org>]

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

Ryan Merriman commented on METRON-1216:
---------------------------------------

I like Simon's idea of using the index configs to build a list of indices for the Alerts UI to query.  You have to have an index config for Metron data to get into ES and it also contains the name of the index (which could be different from the sensor name).  I would take it a step further and add a function that allows a user to override the list of indices that should be included.  METRON-1085 (currently under review) introduces the ability to persist user profile data and could be used for this purpose.  I also like Otto's idea of abstracting this with a REST endpoint.

> ALERT-UI should not hard code sensor indices 
> ---------------------------------------------
>
>                 Key: METRON-1216
>                 URL: https://issues.apache.org/jira/browse/METRON-1216
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Otto Fowler
>
> Right now, the indices that the ALERT-UI uses for searches is hard coded.  This means the alert ui cannot support other sensors in the project outside of those parsers, nor can it support user define sensors.
> The rest api should expose a method of getting the indices, and the alert ui should use this information when building queries.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)