-
-
Notifications
You must be signed in to change notification settings - Fork 119
+ Add UptimeRobot all monitors features #632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
| } | ||
|
|
||
| return nil, nil | ||
| } else if response.StatusCode == Http.StatusTooManyRequests { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a maintainer or anything but I'm interested in the addition of the missing UptimeRobot features, thanks for the PR!
I'm just wondering, why did you remove the code to handle HTTP 429 response status?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My bad I think
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have rollback the missing parts in the last commit.
Thanks @eneiss for your review !
I hope someone can help these features be part of the project asap.
Best regads,
Didier
|
Up ! Is someone available to review this ? |
|
Up ? |
|
@dsegurakaliop I'm trying to use your PRs (but unfortunatly I'm not a maintainer so I can't help that much on merging this)
Eager to see this PR merged @MuneebAijaz ? |
| // Alert Contacts (Optional) | ||
| if providerConfig != nil && len(providerConfig.AlertContacts) != 0 { | ||
| body += "&alert_contacts=" + url.QueryEscape(providerConfig.AlertContacts) | ||
| } else { | ||
| body += "&alert_contacts=" + url.QueryEscape(monitor.alertContacts) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be removed (duplicates of lines 231-235), generates an error: "Error: "alert_contacts" must be a string"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
| // Interval (Optional, in seconds) | ||
| if providerConfig != nil && providerConfig.Interval > 0 { | ||
| body += "&interval=" + strconv.Itoa(providerConfig.Interval) | ||
| } else { | ||
| body += "&interval=" + strconv.Itoa(DefaultInterval) | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be removed (duplicates of lines 237-242), generates an error: "Error: "interval" must be a string"
|
Hi, will hopefully take a look at the PR this week. Thanks for the contribution |
Felix-Stakater
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of small changes are required before we can merge this, thanks for your contribution! :)
| } | ||
|
|
||
| // Interval (Optional, in seconds) | ||
| if providerConfig != nil && providerConfig.Interval > 0 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As @dguihal commented we need to remove this block
| // Alert Contacts (Optional) | ||
| if providerConfig != nil && len(providerConfig.AlertContacts) != 0 { | ||
| body += "&alert_contacts=" + url.QueryEscape(providerConfig.AlertContacts) | ||
| } else { | ||
| body += "&alert_contacts=" + url.QueryEscape(monitor.alertContacts) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
|
Big thanks for this active review and fixes. Sorry if I have done some mistakes, I really want these features appears one day, and I think we are now very close ! Thanks everyone. |
|
Hi @dsegurakaliop I created a PR on your fork dsegurakaliop#1 I've managed to make this code run properly on a dev env |
|
Hey @dguihal thanks for effort. Can you do us a favor and open pull request towards us so it can be reviewed, tested and possibly merged as enhancement? |
|
Hi @mahmadmujtaba I created #655 |
If someone can test the integration of these new features, it will be really GREAT !
I have done all I can from my little experience in GO world.
Please be free to add your stone !