meteor/oncall-bot

Name: oncall-bot

Owner: Meteor

Description: Sync a PagerDuty schedule's current on-call to a Slack channel's topic (implemented in Meteor)

Created: 2017-04-27 22:33:33.0

Updated: 2017-06-11 19:08:25.0

Pushed: 2017-06-13 01:07:16.0

Homepage: null

Size: 8

Language: JavaScript

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

This bot maintains a single Slack channel's topic to contain the name of the level-1 on-call user for a given PagerDuty schedule ID.

Create a settings.json file like:


agerduty": {
"scheduleID": "ID",
"pagerdutyToken": "TOKEN"

lack": {
"channelName": "galaxy-alerts",
"slackToken": "TOKEN1",
"slackAdminToken": "TOKEN2"

ntervalMS": 30000,
tatusUsers": {
"U02FWGZ19": "glasser@meteor.com"


Users listed (by Slack ID) in the status section will have their status text and emoji set as configured when they are on call, and cleared if they are not on call any more and their status starts with 'On call!'. (If they already have a status, it is appended to the 'On call!' status text along with its emoji, and restored when they go off call.)

The simplest way to find a Slack ID is to run users.list via the Slack API tester and find the id field corresponding to the user.

Deploy to Galaxy. (This is deployed to galaxy-primary-oncall-bot.meteorapp.com.)


This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.