Skip to content
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

call_person puts previous person on call temporarily #44

Open
dbenamy opened this issue Dec 2, 2016 · 1 comment
Open

call_person puts previous person on call temporarily #44

dbenamy opened this issue Dec 2, 2016 · 1 comment

Comments

@dbenamy
Copy link
Contributor

dbenamy commented Dec 2, 2016

I set up a temp service, escalation policy, and schedule for use by pagerbot. I tested it, which put me on call for 5m, and it worked. Much later, I did @pagerbot get someone_else whatever, and I got a notification from pagerduty that I was going on call, and then right after, I got the going off call notification. The incident that it created did get assigned to the someone else.

Is this a known thing?

@macobo
Copy link
Contributor

macobo commented Dec 2, 2016

That's curious, is this reproducible?

Since pagerbot API can't call people directly, the hack we do is put them on call for a short period and them trigger an incident. Code here: https://github.com/stripe-contrib/pagerbot/blob/master/lib/pagerbot/plugin/call_person.rb#L79

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

No branches or pull requests

2 participants