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
Аbstract In current implementation each alert looks like a new alert. We can't understand is it new or not without reading and understanding it.
Motivation and Purposes Alerts chains can help us to determine which alert is first in chain and when a problem has been appeared.
Specification We have similar implementation with Resolved alerts type. I propose to scale this logic to any repeating alert.
Resolved
Backwards Compatibility To support backward compatibility we should send a regular alert message if we don't have an ID of previous alert in chain.
The text was updated successfully, but these errors were encountered:
esuwu
No branches or pull requests
Аbstract
In current implementation each alert looks like a new alert. We can't understand is it new or not without reading and understanding it.
Motivation and Purposes
Alerts chains can help us to determine which alert is first in chain and when a problem has been appeared.
Specification
We have similar implementation with
Resolved
alerts type. I propose to scale this logic to any repeating alert.Backwards Compatibility
To support backward compatibility we should send a regular alert message if we don't have an ID of previous alert in chain.
The text was updated successfully, but these errors were encountered: