THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Info | ||
|---|---|---|
| ||
Welcome to contribute improvement proposal by sending discussion to dev@eagle.incubator.apache.org ! |
| Table of Contents |
|---|
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
...
JIRAS
| Jira | ||||||
|---|---|---|---|---|---|---|
|
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.