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

Compare with Current View Page History

« Previous Version 9 Next »

EIP-1: UI Improvements


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

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.
  • API paths are not well organized like "/metadata" or "/coordinator"

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

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