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

[epic-Incident Management] #1

Closed
lmilbaum opened this issue Jan 15, 2019 · 3 comments
Closed

[epic-Incident Management] #1

lmilbaum opened this issue Jan 15, 2019 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@lmilbaum
Copy link
Collaborator

lmilbaum commented Jan 15, 2019

Delivery Pipeline is a multi sub-services service. Each sub-service may through alerts when hitting a failure or close to hitting one.

The alerts should be pushed to a one and only one queue. This is the first sub-service.

The queue should be able to:

  • Consume the alerts and transform them to incidents

  • Analyze the alerts - removing false/positives and aggregation of similar alerts

  • Tracking incidents are resolved according to SLA

  • Remediation by automation

@lmilbaum lmilbaum added the enhancement New feature or request label Jan 15, 2019
@lmilbaum lmilbaum changed the title [epic] Incident Management [epic-Incident Management] Jan 15, 2019
@lmilbaum
Copy link
Collaborator Author

@lmilbaum lmilbaum self-assigned this Jan 15, 2019
@lmilbaum
Copy link
Collaborator Author

Are we taking care of spawning the environment or starting from an existing environment?

@bregman-arie
Copy link
Contributor

I would vote for taking care of the spawning as it makes it easier to test the project in the future + best customer experience :D

lmilbaum added a commit that referenced this issue Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants