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
health: make Opsgenie API URL configurable #10561
Conversation
Add OPSGENIE_API_URL="" to specify API endpoint
Add URL for sanity
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.
Add default value of https://api.opsgenie.com for OPSGENIE_API_URL when unset Substitute OPSGENIE_API_URL for URL on line 2182
Re-added parenthesis deleted in error on ln 2180
Amend to reflect OPSGENIE_API_URL variable
Remove hardcoded URL as now has default if unset
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.
OK should be good to go, even replaced the ) I deleted by mistake 😂
Thanks for the work on this. It looks good to go from my perspective, but as of right now is probably not going to be merged until after the v1.29 release (currently scheduled for tomorrow) as we’re in a code freeze right now in preparation for the release and the hardcoded URL is not exactly a critical bug. |
Yeah, no worries @Ferroin. |
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.
Docs part of this LGTM!
Hello @tinyhammers , I tested your PR right now with the old configuration I had from OPSGENIE, with this old configuration I had only
Considering this, the changes you brought is not keeping compatibily with old configuration, please, can you take a look on this before we merge your PR? |
Moved OPSGENIE_API_URL=${OPSGENIE_API_URL:-"https://api.opsgenie.com"} from line 394 to line 415 as per comment netdata#10561 (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.
After the last commit, I can verify that everything is working with old configuration.
Thank you very much @tinyhammers !
The merge of this will either have to wait until we’re out of the post-release soft code freeze, or would require changing the target branch from @tinyhammers It’s up to you whether you want to wait the week or two for the soft freeze to end or just rebase on top of |
Happy to wait :) |
Now that we got the release out, we are good to go @Ferroin ? |
We’re waiting until tomorrow (2020-02-11) to verify that no other major bugs are discovered after the recent patch release, but this PR is right at the top of my list to merge once the code freeze is over. |
* Update health_alarm_notify.conf Add OPSGENIE_API_URL="" to specify API endpoint * Update health_alarm_notify.conf Add URL for sanity * Update alarm-notify.sh.in Add default value of https://api.opsgenie.com for OPSGENIE_API_URL when unset Substitute OPSGENIE_API_URL for URL on line 2182 * Update alarm-notify.sh.in Re-added parenthesis deleted in error on ln 2180 * Update README.md Amend to reflect OPSGENIE_API_URL variable * Update health_alarm_notify.conf Remove hardcoded URL as now has default if unset * Update alarm-notify.sh.in Moved OPSGENIE_API_URL=${OPSGENIE_API_URL:-"https://api.opsgenie.com"} from line 394 to line 415 as per comment netdata#10561 (comment)
Add OPSGENIE_API_URL="" to so user can specify API endpoint
Summary
Fixes: #10556
Component Name
Test Plan
This has been tested on our production infrastructure and is working
Additional Information