You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 43 Next »

Contribution

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

EIP-1: UI Improvements

Owner: Jilin, Jiang

Improvements

  • Support eagle application status auo-sync
  • Add app configuration view page
  • Policy creation failed and show 'Policy 'test_delete' not found!'
  • Support policy validation function when submitting policy in advanced mode.
  • Hide "start/stop" button for un-executable application
  • Add dedup fields in policy definition page
  • Enrich application status with colorful icon label 
  • Refactor view policy page (basic, definition, execution) Hao Chen
  • Add installed application view page (Desc, Status, Execution)
  • Integrate install/uninstall docs to cooresponding process instead of on ApplicationDesc.
  • Add "Guide" tab aside "Environment" and "Configuration" during Installation/Uninstallation accordingly, contains Installation/Uninstallation guide and dependency status.
  • Improve execution visibility
    • Policy deployed assignments and execution metrics
    • Application running  status, metrics and physical information (storm info/tracking url/metric)
    • Alert Engine backend visibility (Topology/Policy distribution/Worker load visualization)
  • Move Streams (Installed Streams) to Alert

Policy Editor

  • 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
  • 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)
  • Create Publisher in Popup Dialog and Add Publisher list page

JIRAS

type key summary assignee reporter priority status resolution created updated due

JQL and issue key arguments for this macro require at least one Jira application link to be configured

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.

 

 

  • No labels