Versions Compared

Old Version 55

changes.mady.by.user Hao Chen

Saved on

compared with

New Version Current

changes.mady.by.user Hao Chen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info
titleContribution

Welcome to contribute improvement proposal by sending discussion to dev@eagle.incubator.apache.org !

EIP-1: UI Improvements

Owner: Jilin, Jiang

Improvements

  •  
    EIP-1.1 Support eagle application status auo-sync (reported by Hao Chen)
  •  
    EIP-1.2 Add app configuration view page (reported by qingwzhao)
  •  
    EIP-1.3 Policy creation failed and show 'Policy 'test_delete' not found!' (reported by Hao Chen)
  •  
    EIP-1.4 [API Require] Support policy validation function when submitting policy in advanced mode. (reported by Hao Chen)
  •  
    EIP-1.5 Hide "start/stop" button for un-executable application (reported by Hao Chen)
  •  
    EIP-1.6 Add dedup fields in policy definition page (reported by qingwzhao)
  •  
    EIP-1.7 Enrich application status with colorful icon label  (reported by Hao Chen)
  •  
    EIP-1.8 Refactor view policy page (basic, definition, execution) (reported by Hao Chen)
  •  
    EIP-1.9 Add installed application view page (Desc, Status, Execution) (reported by Hao Chen)
  •  
    EIP-1.10 [API Require] Integrate install/uninstall docs to cooresponding process instead of on ApplicationDesc. (reported by Hao Chen)
  •  
    EIP-1.11 Add "Guide" tab aside "Environment" and "Configuration" during Installation/Uninstallation accordingly, contains Installation/Uninstallation guide and dependency status. (reported by Hao Chen)
  •  

    EIP-1.12 Improve execution visibility (reported by Hao Chen)EIP-1.13 Move Streams (Installed Streams) to Alert (reported by Hao Chen) 

     

    •  EIP-1.12.1 [API Require] Policy deployed assignments and execution metrics
    •  EIP-1.12.2 [API Require] Application running  status, metrics and physical information (storm info/tracking url/metric)
    •  EIP-1.12.3 [API Require] Alert Engine backend visibility (Topology/Policy distribution/Worker load visualization)
  •   
  •  

    EIP-1.14 app settings enhance (reported by Hao Chen)EIP-1.15 RefactorPolicy Editor (reported by Hao Chen)

    •  EIP-1.14.1 Rename "Configuration" as "Settings"
    •  EIP-1.14.2 Separate settings items to different section: Basic Settings (required = true), Advanced Settings (required = false), and  Additional Settings (key=value)
    •  EIP-1.14.3 Show  setting name as "displayName" and (?) which show configuration name and description as tips.
    •  EIP-1.14.4 Add additional configuration with two-inputs form: Name + Value
  •  EIP-1.15 Refactor Policy Editor
  •   

...

    •  
      EIP-1.15.1 Support select output stream according to Siddhi query instead of forcing user to input, by default OUTPUT_STREAM_LIST = ALL_STREAM_LIST - INPUT_STREAM_LIST
    •  
      EIP-1.15.2 Refactor layout as: Basic (Name, Desc) -> Policy Definition (Siddhi)  ->  Connect From (Automatically generate according to query and support edit partition per stream)  -> Alert On (select from output stream) -> Publish To (Select Publisher)
    •  
      EIP-1.15.3 Create Publisher in Popup Dialog and Add Publisher list page

...

JIRAS

Jira
serverASF JIRA
jqlQueryproject = EAGLE AND status in (Open, "In Progress", Reopened) AND affectedVersion = v0.5.0 AND assignee in (smith3816)
serverId5aa69414-a9e9-3523-82ec-879b028fb15b

EIP-2: Refactor Alert WebService API

Owner: Hao Chen

The alert web service API has some problems like:

  • Unmanaged (raw status/message) response structure, which cause inconsistent behaviors for client side and UI side
  • All alert metadata are coupled in "IMetadataDao" interface and provide only RAW rest API but not business-logic oriented API.

EIP-3: Use consistent namespace concept for eagle and alert engine

Owner: Hao Chen

Problem

"site" in eagle means an isolated monitored namespace for certain tenant, like a monitored cluster or service.
In most cases, we could simply make sure a policy/application is owned by certain site, for example, alert policies are often bound with certain site which will be much easier for user to organize them, as well as applications, but there are also some special cases where polices/applications may also cross different sites, for example alert engine app in fact is shared by all sites, as well as some global overview dashboards.

Proposal

Keep a reserved "default" site, which means "a globally shared namespace", so that we could simply use consistent metadata structure for site-based / non-site / cross-site cases cases.

 

Links

Table of Contents