-
Notifications
You must be signed in to change notification settings - Fork 171
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
Updated to use the new Pagerduty API library, which allows resolving incidents. #353
base: master
Are you sure you want to change the base?
Conversation
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.
Thanks for the PR I have a few comments.
LOG.warning('PagerDuty notice sent') | ||
|
||
def status_change(self, alert, status, text, **kwargs): | ||
LOG.warn('PagerDuty status change ignored.') |
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.
Why would you ignore status changes?
def post_receive(self, alert): | ||
def post_receive(self, alert, **kwargs): | ||
|
||
LOG.warning('Sending PagerDuty notice') |
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.
Why does this need to be a "warning" ?
except Exception as e: | ||
raise RuntimeError("PagerDuty connection error: %s" % e) | ||
|
||
LOG.debug('PagerDuty response: %s - %s', r.status_code, r.text) | ||
LOG.warning('PagerDuty notice sent') |
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.
Probably shouldn't be a warning. "info" or "debug"?
No description provided.