Pagerduty audits are to be completed every 6 months:
This is a simpler audit, since it is mostly just checking for valid IDs and schedules. As this doesn't require much human interaction, it is largely scripted.
To get started, you will first want to make an issue using the Pagerduty issue template in the audits project.
To start, you will want to run the
pagerduty audit script
(see below for help with running the script). Once the
script completes, it will output a large amount of information. This should be
copied and pasted into the
## Notes section of the issue you created via the
Pagerduty issue template.
From there, you need to go through the items reported and ping the person in the issue to ask for the item to be fixed (or clarify if this is intentional). This can take time, so wait about 72 hours after pinging someone before following back up. If the person has not replied concerning the topic by that time, ping that person's manager (as well as the Support Operations Manager).
Once all the items have been addressed, you will then ping a Support Operations Manager to review the audit. They will then close out the issue.
The requirements to run the script are:
To run the script, you will want to do the following commands:
git clone firstname.lastname@example.org:gitlab-com/support/support-ops/audits.git cd audits gem install bundler bundle install ./bin/pagerduty_audit
NOTE: This uses environment variables to run. As such, you'd want to set the following environment variables:
PD_TOKEN- The Pagerduty API token to use
GL_TOKEN- The GitLab.com access token to use
As the script output is quite large, you might want to have it output to a file so you don't lose the data due to scrollback. This can be done by doing the following:
./bin/pagerduty_audit > audit_output.txt
As it goes through the agents from the support-team.yaml file, it checks the following: