0023490: Alert Management window doesn't scale - Openbravo Issue Tracking System

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0023490

Openbravo ERP

A. Platform

public

2013-04-04 12:50

2013-04-04 12:51

Reporter

alostale

Assigned To

AugustoMauch

Priority

urgent

Severity

major

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0023490: Alert Management window doesn't scale

Description

Alert Management window has some design defects that cause it not to scale in case the amount of alerts is high.

1. When the window is opened, AlertManagementActionHandler is invoked. It is in charge of retrieving the list of alert rule that apply to current user/role (which in general shouldn't be big enough to cause problems). In case the Alert Rule has a Filter Clause, a list of *all* alert instances applicable to the user/role is retrieved, this is very prone to be problematic (see issue 0023482).

2. The information obtained from AlertManagementActionHandler is sent back to datasource for each of the four grids displayed in the window, so the query in backed in composed based on this info.

3. Datasource for "Solved" grid (which is closed by default) is requested on window opening. This grid keeps a history of all alerts, so it can be huge and it is rarely opened.

Steps To Reproduce

Proposed Solution

Below proposed solution for each of the items in the description.

1. AlertManagementActionHandler shouldn't retrieve the instances of all alerts, and ideally not even the alert rules.

2. Instead of using a standard datasource, a manual one could be used. This one would do all the stuff currently AlertManagementActionHandler is doing. So the only required parameter would be the grid type.

3. Do not request "solved" grid till it is opened in the UI.

Additional Information