mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 23:15:49 +03:00
[GH-ISSUE #51] Notifications not being sent. #26
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#26
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 @stevenmcastano on GitHub (Apr 4, 2016).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/51
I've added a little bit of code and got healthchecks to the a local postfix install via an GMail smarthost to send emails, config here:
I've got a check purposefully set VERY small, set to come in every 1 minute with a 1 minute grace. The web interface shows the checks late, then it shows them missing, but the email never goes out.
I know the email config works because when I entered my email it correctly sent the confirmation email. Is there something I need to change somewhere?
@cuu508 commented on GitHub (Apr 5, 2016):
Hi Steven,
are you running the
manage.py sendalertscommand?@stevenmcastano commented on GitHub (Apr 5, 2016):
Well sun of a gun, I was not!! As soon as I fired it up, it started working! That’s great!!
Is there a link to some more detailed documentation on how to do things like logging in as the super user? Customizing email templates? Possibly writing web hooks with variable in them?
I have a pretty sophisticaed python application that I call “Notification Central”, that currently takes REST API commands in and allows you to pick which services you want to send a notification out through, pushover, pushbullet, email, growl, XBMC/Kodi, SMS (via google voice of Twilio), etc… and allows you send in a title, subject, message priority and a “selection code” to choose which, if not multiple of the services you’d like the notifications to go out out as. It takes inputs from the HTTP API and can also take inputs as if it was a Growl node.
Is there any easy way of integrating something like? I was thinking the easiest would be through the web hooks but couldn’t find any documentation on how/if you could but variables into the web call itself. Then to be honest, I’d love to have one call for “Down” situations, another for “Up” so the priority could be set different which translates in my software to different sounds, longer onscreen message time, etc.
Also, is there a way to block people from making new registrations? And how exactly does the superuser account log in?
*SMC
@stevenmcastano commented on GitHub (Apr 5, 2016):
Oh… and of course, THANKS so much for the quick reply… with this working now, this is EXACTLY the type of solution I’ve been looking for!!!
*SMC
@stevenmcastano commented on GitHub (Apr 5, 2016):
Jeez… one last thing I forgot to ask… I see a way in there to convert things over to MySQL which would be so much better since I already have a cluster setup with nightly backups (a script a plan to use this to monitor), how would I switch the backup to MySQL from postgres?
*SMC
@cuu508 commented on GitHub (Apr 5, 2016):
Django administration is at http://localhost:8080/admin – added a note about this to README.
Have not looked into this. You can of course just fork the repo and edit the templates, but then you'll have to do some merging going forward. There might be a better way to do this.
Can you please open a separate issue for this? I'm guessing the interesting variables would be check's status (up/down) and its name and code.
Cool, that's the type of application I added the webhooks support for. If we need to post more data to make the integration useful, we'll do that.
Not at the moment... What use case are you thinking of?
I updated the README with details on this.
Good stuff, happy to hear that!
@stevenmcastano commented on GitHub (Apr 5, 2016):
This all looks like GREAT stuff... thanks again for all your replies!! I just got pulled into a little bit of an emergency at one of my dataacenters, but I'll be back to look at everything you just posted about ASAP and I'll keep you updated!
I'm super pumped that I found this project, GREAT work so far!!
@stevenmcastano commented on GitHub (Apr 6, 2016):
Basically, I'd want the site to almost be invite only, so I could have it publicly acessible, but only allow users from my company to log in... via invite code, or simply have to just create the account for them buy putting in there email or something.
As for the mysql stuff... AWESOME, that looks like it worked perfectly, I just need to handle the requirements.txt so it stops trying to build all the postgres stuff... I might just try to move my code over.
@cuu508 commented on GitHub (Sep 12, 2017):
I had added a
REGISTRATION_OPENsetting a while back. I think it covers this issue.From README: