Skip to content
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.

Downtime is not respected #368

Open
rajatparida86 opened this issue Oct 2, 2018 · 1 comment
Open

Downtime is not respected #368

rajatparida86 opened this issue Oct 2, 2018 · 1 comment
Labels
bug user-reported issues that take more than one hour to resolve

Comments

@rajatparida86
Copy link

rajatparida86 commented Oct 2, 2018

User complains about having problems with down timing an alert Internal ref:133

It is triggered for an instance (which is ok because the condition is met), but I would like to postpone fixing it so I put it to downtime for the entity.
It worked for some time but after some hours the alert is triggered again for the same entity, even that the downtime was not yet finished. So I put it to downtime again and after some hours this repeats, so I have multiple active downtimes for the same alert and same entity (currently 3 at the moment).

@rajatparida86 rajatparida86 added the bug user-reported issues that take more than one hour to resolve label Oct 2, 2018
@aermakov-zalando
Copy link
Contributor

Any updates on this? It's happening pretty much every time we try to set a downtime.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug user-reported issues that take more than one hour to resolve
Projects
None yet
Development

No branches or pull requests

2 participants