mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 06:55:53 +03:00
[GH-ISSUE #391] integration stay red until next message is send even if test succeeds #295
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#295
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SuperSandro2000 on GitHub (Jun 30, 2020).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/391
I am self hosting my healthchecks and after a connectivity issue a few of my integrations are red. They didn't turn back green when I tested them to see if they are working. I think this should be added cause they should not stay red until the next real alarm is send.
@cuu508 commented on GitHub (Jul 1, 2020):
Thanks for the suggestion, makes sense.
I changed how the "Test!" button works:
@SuperSandro2000 commented on GitHub (Jul 1, 2020):
Thanks!
Does this also mean both notification are send from the same process?
@cuu508 commented on GitHub (Jul 1, 2020):
No, normal notifications are sent by the
manage.py sendalertsprocess. Test notifications are sent by the web server process while handling the HTTP request.@SuperSandro2000 commented on GitHub (Jul 1, 2020):
Good to clarify that. I noticed this error initially while debugging this.