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 upAlerts are not recovered,but endsAt field shows a valid time. #3231
Comments
This comment has been minimized.
This comment has been minimized.
|
I don't see anything wrong here, this is what it looks like when an alert is resolved. What did you expect to happen? |
brian-brazil
added
the
kind/more-info-needed
label
Oct 18, 2017
This comment has been minimized.
This comment has been minimized.
|
From the time series,we can see that the value of the metric is always 1,which will trigger alerts but from alert info ,it shows that the alert has been resolved which is not true. thanks |
This comment has been minimized.
This comment has been minimized.
|
This is correct, you've a gap in your data around then. |
brian-brazil
closed this
Oct 19, 2017
This comment has been minimized.
This comment has been minimized.
|
Why a gap should be treated as resolved? |
This comment has been minimized.
This comment has been minimized.
|
The alert stopped firing as there was no data. |
This comment has been minimized.
This comment has been minimized.
codwu
commented
Dec 13, 2017
|
@brian-brazil If I got a resolved alert, How can I know whether it is really resolved or there is no data? |
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 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. |
empo007 commentedSep 30, 2017
What did you do?
What did you expect to see?
Alert rule is defined as following:
the alert should never ends. all time series are here:
What did you see instead? Under which circumstances?
Environment
Linux 2.6.32-573.el6.x86_64 x86_64
prometheus, version 1.6.3 (branch: master, revision: c580b60)
build user: root@a6410e65f5c7
build date: 20170522-09:15:06
go version: go1.8.1
Alertmanager version:
insert output of
alertmanager -versionhere (if relevant to the issue)Prometheus configuration file: