Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best Practice rule failures (evaluations?) need to generate events and be searchable. #19

Open
Alan-R opened this issue Dec 18, 2015 · 2 comments
Assignees

Comments

@Alan-R
Copy link
Member

Alan-R commented Dec 18, 2015

See: https://trello.com/c/XRhZqwWu

  • Events: One event should be generated for each new failure and each new success. Currently these events are ephemeral, but eventually will be persistent.
  • Searchable. A relationship or node should exist for each failure, and maybe for each success. The general idea is that one should be able to easily search for all systems that failed tests, a total count of failures should be available, and it should be possible to collect the list of machines with any failure, or those which fail any given rule.
Alan-R added a commit that referenced this issue Dec 30, 2015
Issue #19: Introduce UNWARN event/add event sending to best practices
@Alan-R
Copy link
Member Author

Alan-R commented Dec 30, 2015

Dave's #19 commit addressed the first issue, but not the second. He'll get to that later...

@Alan-R
Copy link
Member Author

Alan-R commented Jan 12, 2016

This item is closed since the first part (generate events) is done. #25 comprises the second half (searchable) of this work item.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants