Coverage request (🤝)
Oncall User Group (@mention current on-call)
Settings
<aside> 📣 We’d love to hear from you: Our indie team is working to enable “Painless On-Call” so development teams and engineers can do what they do best - build. We’d love to hear from you on how we can help make PagerDuty work better for you and your team.
</aside>
<aside> ☎️ General support, questions, or feedback: [email protected] Or, let’s talk: Pick a time for a call from our calendar
</aside>
It’s the missing Slack tools you’ve always wanted for PagerDuty. 💚 📟
Requirements note: Our PagerDuty integration requires an Admin base role for account authorization. If you do not have this role, please contact an Admin or Account Owner within your organization to configure the integration. All active users must have Slack and PagerDuty accounts using the same email addresses.
⌚ A note on dates & times: SunChaser shows all dates & times in your timezone. Please enter any date/time request in your time zone. Any time zones added to commands will be stripped out.
@SunChaser
Slack bot into any private channels that you linked.All done. Everyone on the team has access to SunChaser. Try /sunchaser oncall
in any channel to see everyone currently on-call. 😎
Note: You must have an Admin base role for PagerDuty to authorize the integration.
You must have a Slack Workspace account (& you may need to be an account admin). Please contact your Slack account administrator if you cannot add apps to your Slack workspace. For more information about installing apps, see [Slack’s help documentation](https://slack.com/help/articles/360001537467-Guide-to-apps-in-Slack#:~:text=Add apps to your workspace,submit an app request instead.).
From any channel, see who’s on call for all escalation policies enabled for SunChaser via a private message.
/sunchaser oncall [DATE] [@USER]
DATE
is optional, and the default DATE
is now. DATE
format examples: 11/01 (MM/DD), Nov 1st, Fri 1, November, tomorrow, etc.USER
is optional; this person must have a PagerDuty account.View your next 5 upcoming shifts from any channel within 90 days via a private message. Check your shifts in the future by including a date.
/sunchaser my-schedule [DATE]
DATE
is optional, and the default DATE
is now. DATE
format examples: 11/01 (MM/DD), Nov 1st, Fri 1, November, tomorrow, etc.Get notifications in Slack about your upcoming shifts.
From the SunChaser app home scroll to :reminder_ribbon: “Receive reminders for your upcoming shifts via a Slack DM from SunChaser”. Select your notification timing from the drop-down (1 day, 1 week or 4 weeks notice). SunChaser will DM you your notification setting and your notification ahead of time. Remove notifications by selecting “No notifications” from the drop-down menu.
Need help covering all or part of a shift? Share a shift coverage request. You can optionally specify which schedule by including the schedule ID.
/sunchaser coverage [SCHEDULE_ID] START – END
/sunchaser my-schedule
SCHEDULE_ID
.SCHEDULE_ID
to your command to request coverage for a specific tier (e.g., Secondary schedule). This is required in un-linked channels, or channels linked to a different escalation policy./sc my-schedule
to copy and paste exact times.Make a one-time adjustment to a PagerDuty schedule by creating an override from any channel in Slack that SunChaser has been invited to.
/sunchaser override SCHEDULE_ID START – END @USER
/sunchaser schedules
SCHEDULE_ID
is required. But, if this command is run in a 🤝 linked channel, it is optional and assumed to be the first-tier schedule./sunchaser schedules
START – END
is required; format examples: Monday 2 pm – 5 pm, 11/01 – 11/08, Nov 1st 3pm – 8th 3pm PDT, Tomorrow.@USER
is the Slack name for the person who will be added to the schedule; this person must have a PagerDuty account.Oncall User Groups create an @mention that always mentions the current person on call.
To set up Oncall User Groups:
/sunchaser help
/sunchaser oncall [DATE] [@USER]
/sunchaser my-schedule [DATE]
/sunchaser escalation-policies
/sunchaser schedules
/sunchaser override SCHEDULE_ID START – END @USER
/sunchaser coverage [SCHEDULE_ID] START – END