mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-26 07:25:51 +03:00
[GH-ISSUE #285] add_pushover logic seems completely broken #215
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#215
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 @anymuster2 on GitHub (Sep 5, 2019).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/285
The logic in the function add_pushover ( https://github.com/healthchecks/healthchecks/blob/master/hc/front/views.py#L1060 ) doesn't make a lot of sense. I cannot get it to add a valid Pushover entity.
I'm unclear on what the intended purpose of PUSHOVER_SUBSCRIPTION_URL is, but POST seems to redirect to that URL (when judging by other functions, a POST should create a
Channeldb entry).There's also a spelling error in a h1:
Also, assuming you're the owner of pushover.io, just a heads up that in 'Billing' my account says 'Checks: n / 500' but under pricing it says I'm limited to 20 :)
@cuu508 commented on GitHub (Sep 5, 2019):
The Pushover integration setup works like this:
PUSHOVER_SUBSCRIPTION_URL)pushover_user_key) in query stringChannelobject and stores the credentialsMore details: https://pushover.net/api/subscriptions#web
Can you please describe step by step what you're doing and what you're seeing (any error messages?)
Fixed the spelling error – thanks!
Did you by any chance create your Healthchecks.io account long ago (2017 or before)?
When I was making changes to pricing and account limits, I made sure to "grandfather" the existing users.
@anymuster2 commented on GitHub (Sep 5, 2019):
Ah, that makes sense - coming from other services, I expected to create a pushover API code and add that to the local healthchecks instance manually.
Could you please give a demonstration of correct PUSHOVER_SUBSCRIPTION_URL and PUSHOVER_API_TOKEN values? (On Pushover Dashboard I have a 'User Key' and per-'application' API keys)
Edit:
I made sure to "grandfather" the existing users.That would be it, I only use one check which is to monitor my local healthchecks server :P@cuu508 commented on GitHub (Sep 5, 2019):
To enable Pushover integration on your instance, you will need to:
subscription type
Pushover will then show you the values to use as
PUSHOVER_API_TOKENandPUSHOVER_SUBSCRIPTION_URL.@anymuster2 commented on GitHub (Sep 7, 2019):
I've gotten slightly further, but Pushover doesn't redirect back to my local healthchecks instance. The URL my healthchecks redirects to Healthchecks with is as follows (sorry for the redactions)
https://pushover.net/subscribe/MyHCAppName-RandomKeys?success=http%3A%2F%2Fredacted%2Fintegrations%2Fadd_pushover%2F%3Fstate%3DRandomChars%26prio%3D0%26prio_up%3D0&failure=http%3A%2F%2Fredacted%2Fintegrations%2FOn opening Healthchecks, it prompts me to subscribe to the app, on clicking 'subscribe me' I get redirected to https://pushover.net/ which renders my landing dashboard (app list, api keys, settings etc)
@cuu508 commented on GitHub (Sep 9, 2019):
In Pushover, Edit Application > Edit Subscription Settings, have you selected Subscription Type = URL?
@anymuster2 commented on GitHub (Sep 9, 2019):
Thanks that's fixed it :) See the above PR feel free to reject if you don't see it as appropriate.
@nightah commented on GitHub (Nov 7, 2019):
@cuu508 I don't mean to necro bump an old thread but has something changed with the pushover integration?
I've followed the respective steps but when healthchecks redirects to Pushover I get an error stating:
The link constructed by healthchecks to send to Pushover is very similar to the one @anymuster2 posted above, I can see both the
PUSHOVER_API_TOKENandPUSHOVER_SUBSCRIPTION_URLare present and accurate too.EDIT: Nevermind, looks like the issue was because when I first setup healthchecks the
SITE_ROOTvariable didn't include thehttps://string.