[GH-ISSUE #156] sendalerts not sending notificaions #107

Closed
opened 2026-02-25 23:41:12 +03:00 by kerem · 5 comments
Owner

Originally created by @mgeorgy on GitHub (Mar 9, 2018).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/156

I'm using healthchecks in a development environment and am able to send login emails, however, notification emails are never sent. I'm assuming the notifications flow uses the same configuration so not sure why this isn't working properly.

Configuration:

  • Ubuntu 16.04 Server
  • Nginx Reverse Proxy
  • sendalerts is running via a Systemd service process
  • Single Test Check - (checked in once) with a poll period of 1 minute and grace of 1 minute.
  • User account is configured to 'Remind me hourly'

Expected Behavior:

  • Hourly E-Mails send while checks fail

Actual Behavior:

  • No E-Mails Send
  • Console Reports: Alarm (icon); Last ping - '12 hours ago'
Originally created by @mgeorgy on GitHub (Mar 9, 2018). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/156 I'm using healthchecks in a development environment and am able to send login emails, however, notification emails are never sent. I'm assuming the notifications flow uses the same configuration so not sure why this isn't working properly. **Configuration:** - Ubuntu 16.04 Server - Nginx Reverse Proxy - sendalerts is running via a Systemd service process - Single Test Check - (checked in once) with a poll period of 1 minute and grace of 1 minute. - User account is configured to 'Remind me hourly' **Expected Behavior:** - Hourly E-Mails send while checks fail **Actual Behavior:** - No E-Mails Send - Console Reports: Alarm (icon); Last ping - '12 hours ago'
kerem closed this issue 2026-02-25 23:41:12 +03:00
Author
Owner

@cuu508 commented on GitHub (Mar 9, 2018):

You are right, manage.py sendalerts is using the same email settings as the main app.

First thing to check would be the output of manage.py sendalerts command to see if it throws any errors: journalctl -f -u sendalerts-task-name

Also, healthchecks will not send alerts to unverified email addresses -- in the web UI, "Integrations" page you can check if there is "(unverified)" next to the email address.

<!-- gh-comment-id:371808934 --> @cuu508 commented on GitHub (Mar 9, 2018): You are right, `manage.py sendalerts` is using the same email settings as the main app. First thing to check would be the output of `manage.py sendalerts` command to see if it throws any errors: `journalctl -f -u sendalerts-task-name` Also, healthchecks will not send alerts to unverified email addresses -- in the web UI, "Integrations" page you can check if there is "(unverified)" next to the email address.
Author
Owner

@cuu508 commented on GitHub (Mar 9, 2018):

PS. the hourly/daily reminders are sent by manage.py sendreports. If you are looking for the reminders, this command needs to be running as well.

<!-- gh-comment-id:371809323 --> @cuu508 commented on GitHub (Mar 9, 2018): PS. the hourly/daily reminders are sent by `manage.py sendreports`. If you are looking for the reminders, this command needs to be running as well.
Author
Owner

@mgeorgy commented on GitHub (Mar 9, 2018):

Thank you. sendreports worked!

Is it ideal to run this as a cronjob?

<!-- gh-comment-id:371812281 --> @mgeorgy commented on GitHub (Mar 9, 2018): Thank you. sendreports worked! Is it ideal to run this as a cronjob?
Author
Owner

@cuu508 commented on GitHub (Mar 9, 2018):

Good stuff!

Yes, running it as a cronjob is fine. Or, for consistency, you can run it as a systemd process, same way as sendalerts. In that case, you would run it with the --loop flag:

manage.py sendreports --loop
<!-- gh-comment-id:371814954 --> @cuu508 commented on GitHub (Mar 9, 2018): Good stuff! Yes, running it as a cronjob is fine. Or, for consistency, you can run it as a systemd process, same way as `sendalerts`. In that case, you would run it with the `--loop` flag: manage.py sendreports --loop
Author
Owner

@mgeorgy commented on GitHub (Mar 9, 2018):

Perfect! Thanks again.

<!-- gh-comment-id:371828540 --> @mgeorgy commented on GitHub (Mar 9, 2018): Perfect! Thanks again.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#107
No description provided.