We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
The text was updated successfully, but these errors were encountered:
A short related presentation: https://docs.google.com/presentation/d/1yGiGz9NNBYaIlnDj9uhFdk90vnUzELgGKopk7jh7uOc/edit#slide=id.g4baccfa9d2_1_24
Sorry, something went wrong.
Are we taking care of spawning the environment or starting from an existing environment?
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
Merge pull request #1 from lioramilbaum/jenkins-rabbit-kibana
a0f6be0
jenkins-rabbit-kibana
lmilbaum
bregman-arie
No branches or pull requests
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
The text was updated successfully, but these errors were encountered: