Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Decouple AD and Alerting on Kibana #141

Open
ylwu-amzn opened this issue May 14, 2020 · 0 comments
Open

Decouple AD and Alerting on Kibana #141

ylwu-amzn opened this issue May 14, 2020 · 0 comments
Labels
enhancement Enhance current feature for better performance, user experience, etc

Comments

@ylwu-amzn
Copy link
Contributor

Currently we couple AD and alerting on Kibana. We provide specific monitor input type to create monitor on top of detector. But at the backend we just use AD result indices and custom expression to create monitor. User needs to redirect to monitor page to create/view/update/delete/ monitor and view alert details.

We can put monitor creation on AD page. Call monitor creation API from AD Kibana to create monitor. So we can remove the special input type "Define using anomaly detector" and remove all logic related to AD. That will make it easier for AD future design, development and testing.

To save effort, we can still redirect to alerting page for view monitor details, view alerts history.

@ylwu-amzn ylwu-amzn added the enhancement Enhance current feature for better performance, user experience, etc label May 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Enhance current feature for better performance, user experience, etc
Projects
None yet
Development

No branches or pull requests

1 participant