[
https://issues.apache.org/jira/browse/METRON-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Meller updated METRON-2205:
---------------------------------
Description:
Currently, Alerts UI sends a query request to the REST API every time the user
* add new filter
* clear filters
* change time range
This behavior keeps the list of alerts and the state of the filtering in sync:
every time the filter changes the visualized data change with it.
The drawback of this behavior is it fires multiple query requests while the
user tries to set up a more complex filter.
The following scenario:
# clearing the current filter
# changing the time range
# adding a filter for ip_src_addr
# adding a filter for source:type
# pressing the query button
leads 5 queries instead of one. In the case of large data sets, this could lead
to unnecessary load and UI glitches (results update the alerts table with
partially filtered data).
was:
Currently, Alerts UI sends a query request to the REST API every time the user
* add new filter
* clear filters
* change time range
This behavior keeps the list of alerts and the state of the filtering in sync:
every time the filter changes the visualized data change with it.
The drawback of this behavior is it fires multiple query requests while the
user tries to set up a more complex filter.
Tn the following scenario:
* clearing the current filter
* changing the time range
* adding a filter for ip_src_addr
* adding a filter for source:type
* pressing the query button
leads 5 queries instead of one. In the case of large data sets, this could lead
to unnecessary load and UI glitches (results update the alerts table with
partially filtered data).
> Cease querying on filter or time-range change
> ---------------------------------------------
>
> Key: METRON-2205
> URL: https://issues.apache.org/jira/browse/METRON-2205
> Project: Metron
> Issue Type: Bug
> Reporter: Tibor Meller
> Assignee: Tibor Meller
> Priority: Major
>
> Currently, Alerts UI sends a query request to the REST API every time the
> user
> * add new filter
> * clear filters
> * change time range
> This behavior keeps the list of alerts and the state of the filtering in
> sync: every time the filter changes the visualized data change with it.
> The drawback of this behavior is it fires multiple query requests while the
> user tries to set up a more complex filter.
> The following scenario:
> # clearing the current filter
> # changing the time range
> # adding a filter for ip_src_addr
> # adding a filter for source:type
> # pressing the query button
> leads 5 queries instead of one. In the case of large data sets, this could
> lead to unnecessary load and UI glitches (results update the alerts table
> with partially filtered data).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
