GitLab Support On-Call Guide

For customers that have Priority Support, the Support Engineering Team is on-call and available to assist with emergencies

On-call in GitLab Support

There are four on-call rotations in Support:

  • CMOC - in which Support Engineers drive public communication in the incident management process during operational emergencies.
  • Customer Emergencies- in which Support Engineers respond to and coordinate the resolution of emergency reports from Self-managed and customers
  • US Federal Emergencies - which is similar to Customer Emergencies, but has different hours and a US Citizen requirement to participate in
  • Support Manager On-call - in which Support Manager are an escalation point for issues raised by Support Engineers and GitLab team members and missed PagerDuty notifications

For customers that have Priority Support, the Support Engineering Team is on-call in these capacities and available to assist with emergencies. What constitutes an emergency is defined in our definitions of support impact.

We take on-call seriously. There are escalation policies in place so that if a first responder does not respond fast enough another team member or members is/are alerted. Such policies aren’t expected to ever be triggered, but they cover extreme and unforeseeable circumstances.

Expectations for Support on-call

Be alert and available

When you are on call you are expected to be available and ready to respond to PagerDuty pings as soon as possible, and certainly within the emergency response time set by our Service Level Agreements.

If you have plans outside of your work space while being on call, then being available may require bringing a laptop and reliable internet connection with you.

You should not be chained to your desk, but you should be equipped to acknowledge and act on PD alerts in a timely manner.

Be proactive in communicating your availability. Sometimes you can’t be immediately available for every minute of your on-call shift. If you expect to be unavailable for a short period of time, send an FYI in Slack.


Involve relevant stakeholders: whether it’s the e-group, a CSM, subject matter experts or Support leadership, customer and operational emergencies should be known. See your rotation specific workflow for more detailed notes.

Note: You may sometimes be required to contact GitLab users on behalf of another GitLab team (such as the SIRT team). Please follow the Sending Notices workflow to action these requests.

Ask for help when needed

Rest assured: escalation is okay – other GitLab team members are happy to help. Caring for our customers is a shared responsibility. Tag a Slack support-team Group if you haven’t gotten help in your Slack thread. Tag the support managers if you need to escalate further.

If another support engineer joins your emergency call, feel free to assign them a role to divide up the labor.

So and so would you please (take notes, reach out to this product team and ask for help, look up the code for this and see what you can find)?

Take care of yourself

Make a real effort to de-stress during your on-call shift. After being on-call, consider taking time off, as noted in the main GitLab Handbook. Just being available for emergencies and outages causes stress, even if there are no pages. Resting is critical for proper functioning. Just let your team know.

When you get a notification from PagerDuty give yourself a few minutes to prepare.

  • Get to someplace comfortable and quiet where you can devote your attention to the emergency.
  • Take care of any biological needs.
  • Grab a snack and some water.
  • Breathe: you’ve got this.

When you’re in a call, you do not need to provide immediate answers. You’re allowed to pause for a few minutes for researching, asking for help, etc. Make sure to communicate – let the other folks on the call know what you’re doing. Example: “I need a few minutes to work through the code here and make sense of it”.

If you’ve had a long week with multiple pages from PagerDuty or particularly long calls, consider asking someone to cover a day or some portion of a day so you can get some rest.

How Support On-call works

Schedule and escalation policy

By using a regional, follow-the-sun style of on-call Support we try to keep rotations within waking hours. As a result, each region may organize their on-call rotations in a slightly different way, or have different requirements for hours of coverage.

PagerDuty is the single source of truth for on-call hours, rotation order and escalation policies.

NOTE: If a new alert has not been acknowledged after 10 minutes, the Support Manager on-call is alerted. After a further 5 minutes, if there is no acknowledgement, Senior Support Managers are alerted.

There are several ways to view current and future schedules:

  1. On View the current and next week’s assignments
  2. In PagerDuty: View the Customer Emergencies schedule and the escalation policy
  3. In Google Calendar, subscribe to your on-call schedule
  4. In the #spt-gg-forest slack channel, you can see who is on-call for the different schedules today

Changes to PagerDuty rotations or schedules

Changes to PagerDuty schedules will happen once a quarter with additions and removals handled via the Support PagerDuty Worksheet. Permissions on the Worksheet will be limited to Support Management and the Support Operations team.

The Support Operations team will unlock the Support PagerDuty Worksheet at the start of the second month of the quarter. At this time, they will notify the Support Managers and ask them to review and submit changes as necessary. During the final month of the quarter, the Support Operations team will once again lock the Worksheet and implement the changes to go live at the beginning of the next quarter.

When requesting changes to the Shadow schedules, please create a new Issue using the appropriate Issue Template.


When adding someone to the schedule the manager will need to manually add the email address of the user they want added to the rotation.


When removing a user from a schedule the manager will need to delete the email address of the user they are removing, leaving the cell blank.

Your first on-call shift

For new team members approaching their first on-call shift, your Support onboarding issue includes a section suggesting that you shadow a current on-call to gain familiarity with the process. After completing your shadow shift, work with your manager to get yourself added to the on-call rotation. For your first on-call week we recommend asking your Onboarding Buddy to be available as a secondary to help if an emergency comes in.

Make the schedule work for you

Your role is to make sure someone is available to respond to emergencies during the week you are scheduled. Flexibility is possible – you can split work with others, or schedule overrides for a few hours or days. You don’t have to change vacation plans, or be at your desk all week! It’s OK to take a walk outside, if you have your phone and reception. This way you can acknowledge the page, and locate someone to help (using Slack).

If you prefer to work with a colleague as a secondary, discuss with team members or your manager and find partners who like sharing the role. You can work together during the week, and update PagerDuty as you wish (options include: split days into mornings and evenings, take alternate days, work as a primary and secondary). Your manager can play an active role in helping pair people who want to work like this.

Swapping on-call duty

To swap on-call duty with a colleague:

  • Check with your team, see who has availability, and get confirmation from the person willing to cover you. Generally, it’s best to ask for help as far in advance as possible.
  • If you’re unable to find coverage, alert your manager.
  • To swap an on-call shift, or temporarily replace someone, create an override on the main schedule in PagerDuty.
    1. Open the correct schedule in PagerDuty.
    2. Click on the relevant block of time in PagerDuty.
    3. Select “override” and fill in the name of the person you are swapping with.

See the PagerDuty documentation for complete steps.

Considerations in APAC

Shifts start on Tuesday and end on Monday

Due to the global on-call week starting on Monday, 09:00 Amsterdam time, on-call shifts for APAC begin on Tuesday and end on Monday. The APAC team has decided to retain this shift configuration as it allows for easier planning to take a long weekend with Monday off and as a buffer to ease into the next on-call. See the latest discussion in this Support Team Meta issue.

Support Engineer shifts are 4-hour long shifts

APAC spans many timezones. Using an 8-hour shift to cover APAC business hours results in an on-call shift that can finish as late 9pm local time for APAC east based team members, and that starts as early as 04:30 local time for APAC west team members. Consequently the support engineer shifts are split into 2 groups, APAC 1 and APAC 2, allowing each team member to cover hours within their normal working hours.

Note that support manager on call shifts remain the full 8 hours.

Australia (Employees of GitLab PTY Ltd)

Team members employed by GitLab PTY Ltd must take time off in lieu within two weeks of completing their on-call shift. Time in lieu should be requested via Time Off by Deel, selecting the On-Call Time in Lieu option.

For more details, see the GitLab PTY Australia Specific Benefits page.

New Zealand (Employees of GitLab PTY Ltd NZ)

Team members employed by GitLab PTY Ltd NZ must avoid taking an on-call shift which falls on a New Zealand public holiday. If this cannot be avoided, your manager must be informed.

For more details, see the GitLab PTY Ltd NZ Specific Benefits page.

Starting on-call

Before your shift starts, always double-check that your alerts are working and your PagerDuty contact is up to date. Send a test page to make sure that you are receiving alerts correctly.

When your on-call shift starts, you should get notification(s) that your shift is starting (email or text, depending on your PagerDuty preferences).

Ending your on-call shift

Before your shift ends, consider what tasks need to be handed over and make sure to proactively communicate them to the next engineer in the rotation. This may mean paging the next on-call engineer and bringing them into an active troubleshooting call, or it may mean providing instructions or context for situations you have handled that have some follow-up action. For example:

  • if you’re in an active call with a customer and it’s time to end your day, page the incoming on-call and make sure they’re prepared to provide continuity by giving them an overview of what’s been done before and what’s next
    • once you anticipate an active call to spill over into the next shift, try reaching out to the incoming on-call on Slack to make them aware of the upcoming need for a handover – they might not be around already, but it’s worth trying and can make it easier for you to end your shift on time
  • if a SaaS customer paged in looking for log analysis and we’re waiting on the SIRT team, let the incoming on-call know and consider having them send a message in the ticket informing the customer of the handover
  • if a customer is still in a heightened state and is monitoring after an outage and may page the on-call engineer, let the incoming on-call know
  • if a SaaS incident ended and we’re monitoring the queues for new customer reports, provide the incoming on-call engineer with a list of actions they should take

Generally: if there’s a situation that occurred (or is actively happening) during your shift it’s your responsibility to prepare the next on-call engineers.

Some rotations have specific handover procedures:

Viewing all on-call pages in one place

You may want to monitor all on-call pages received by the Support team. You can do this by joining the #spt_on-call Slack channel.

Seeing which manager is on-call

To see who the current manager on-call is you can:

Paging the on-call manager

  • First, try pinging the on-call manager by name in Slack.
  • If it’s important and urgent or a weekend, you can:
    • Use the /pd-support-manager command to page the on-call manager
    • Manually create a new incident from the Support Managers Service

Mobile phone service and data reimbursement

We want to minimize the affect of on-call duty on your life. One way we do that is by offsetting any impact on your personal expenses.

You may expense the cost of your mobile phone service for any month that you are performing on-call duties. This is limited to your service cost itself, not any costs relating to the phone device, to a personal hotspot device or to services for other people on your phone plan.

We understand you may have plans outside of your normal workspace while you’re on-call. If as a result you need to use your phone to provide internet service to your computer, then you may include additional data charges in your expense report.

Keeping the PagerDuty contact up to date

PagerDuty phone and SMS notifications can come from a variety of different phone numbers and as such, it is important to stay up to date with this to avoid missed pages. You should use this PagerDuty documentation page to download the most recent vCard or setup an automatically updated PagerDuty contact on your device.

If you use a “do not disturb” mode on your device, you should also allow the PagerDuty contact to bypass this.

Automatically update your Slack status to indicate you’re on-call

Using the PagerDuty logo as your Slack status can be a helpful indicator to others that you’re currently on-call. We can use Zapier, an automation tool, to update our Slack status automatically when our shift begins. Zapier can connect to PagerDuty directly, but it does not have “Going On-Call” as a trigger – we need to connect to Gmail and use a PagerDuty notification email as the trigger instead.

Configure PagerDuty to send a specific notification email for this automation

To make sure this stays separated from our normal PagerDuty notifications, we’ll set up a notification specifically for this automation.

  1. Go to “My Profile” on PagerDuty
  2. In the “Contact information” tab, click “Add Email Address”
  3. Enter a unique + version of your GSuite email address, like
    • If you do not know about the + trick: This will be delivered to your normal inbox. Specifying this unique version will allow us to create a filter for these notifications later in the process.
  4. Enter anything you want for the “type” (Work, Home, …) – with “Other” you can type your own text
  5. Short/HTML Emails does not make a difference
  6. Add the email address, and use the “Test” button to send a test notification

Adding a new notification email target in PagerDuty

  1. Change to the “Notication Rules” tab
  2. Your new email will already have been added in the “When a high-urgency incident is assigned to me” section – remove it from there, and also from any other sections it might have been added to
  3. Finally, do add it to the “Before I go on-call or off-call” section via the “Add Notification Rule” button
    • Make sure to pick only “before I go on-call”

Setting up a notification specifically for going on-call

That’s step one done – now PagerDuty will always send us a notification mail to the unique email address right when our shift begins.

Configure Gmail to automatically process these new notifications

We do not actually want these notification mails in our inbox, though. They are only a means to an end – so let’s set up a corresponding Gmail filter next.

  1. Go to your Filters and Blocked Addresses settings
  2. With the “Create a new filter” link, start adding the filter
  3. In the To condition, enter your unique email address from above
  4. Click “Create Filter” and choose these actions in the following dialog:
    • Skip the Inbox (Archive it)
    • Mark as read
    • Apply the label: and via the dropdown create a new label of your choice – for example going-on-call
  5. Make sure to check the Also apply filter to x matching conversations box – this should match the test notification we sent earlier
  6. Click “Create Filter” again to actually set it up

It should look like this in your filter list afterwards:

The finished Gmail filter that applies our label

That’s the second step done – we’re now all set to make Zapier use these email notifications as a trigger for the Slack status update.

Configure Zapier to update the Slack status when a new on-call notification email arrives

Note that some teams in GitLab are using Zapier with a paid plan, but Support Engineers usually don’t. There’s no need to for an Access Request and a Zapier license – this works entirely with a free Zapier account.

  1. Sign into (or create an account with) Zapier using your Gmail login
  2. Go to Apps and “Add Connection” for both Gmail and Slack
    • When doing so, you will be prompted to log into both services and give Zapier permissions to access them on your behalf.
  3. Create a new Zap
  4. For the Trigger, use the Gmail app with the New Labeled Email event
  5. Continue until you can pick the “Label/Mailbox” and choose the Gmail label created above (for example going-on-call)
  6. Zapier will now look for emails with that label and should find the test email we triggered earlier
  7. Choose the test email and “Continue with selected record” to start setting up the action
  8. For the Action, use the Slack app with the Set Status event
  9. Continue until you can specifiy the input for the status:
    • Status Text – you’ll likely want to specify your rotation name here
    • Status Emoji – you’ll likely want to use :pagerduty: here
    • Expiration Time – you’ll want to use the duration of your shift here so the status is automatically cleared when your shift is done
  10. In the next step, give it a quick test (don’t forget to clear your Slack status afterwards)
  11. Finally, “publish” your Zap – this is just saving and activating it

Here’s what the result should look like:

The trigger of the zap

The action of the zap

And that was the third and final step – from now on your Slack status should be updating automatically. Due to how this is set up it can sometimes have a few minutes delay, but it’s usually very snappy.