Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Receiving Invalid Parameter Value When Specifying alert_policy #8

Closed
dthagard opened this issue Jun 13, 2017 · 1 comment
Closed

Receiving Invalid Parameter Value When Specifying alert_policy #8

dthagard opened this issue Jun 13, 2017 · 1 comment

Comments

@dthagard
Copy link

This doesn't appear to be a supported attribute on the check types.
See https://www.pingdom.com/resources/api#MethodModify+Check & https://www.pingdom.com/resources/api#MethodCreate+New+Check

When creating a new HTTP check using the latest go-pingdom client, we receive the following error:
400 Bad Request: Invalid parameter value: alert_policy

@russellcardullo
Copy link
Owner

Yeah looking for more information on this but it seems that alert policies aren't enabled for all accounts?

https://help.pingdom.com/hc/en-us/articles/207571825-BeepManager-Incident-and-Alerts

In addition found this which looks like that feature will be removed entirely within the next few months: https://help.pingdom.com/hc/en-us/articles/115000728765-Moving-to-a-Simplified-Pingdom-Alerting-Experience

Since that feature will be going away anyway I think the right thing to do is revert this change so the library works for all users regardless of the account type they have.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants