Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upInvalid resolved timestamps #1386
Comments
fabxc
added
the
bug
label
Feb 12, 2016
This comment has been minimized.
This comment has been minimized.
|
Apparently, this wasn't encountered again and could not be reproduced either. |
fabxc
closed this
Apr 6, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
fabxc commentedFeb 12, 2016
We are encountering an issue where resolved alerts are sent to Alertmanager where the resolved timestamp apprently is not strictly after the start timestamp. These alerts are rejected.
Since this affects resolved alerts, this is non-critical as the affected alerts timeout in Alertmanager by themselves.