Zendesk Global
Documentation on the Zendesk Global system checker
Introduced via gitlab-com/support/support-ops/support-ops-project#1889
Technical Details
- Deployment type:
Ad-hoc - Project repo: gitlab-support-readiness/system-checkers/zendesk-global
Understanding the Zendesk Global system checker
What is the Zendesk Global system checker
The Zendesk Global system checker is a setup using scheduled pipelines to check the status of Zendesk Global. It posts to the #feed_status-zendesk-global Slack channel.
How does it work
At the top of every hour UTC (0 * * * *), a scheduled pipeline causes the bin/run script to execute. This does the following:
- Gathers the current Zendesk status information from the following API endpoints:
- Compares the current Zendesk status information for incidents to that of the stored information from
data/incidents.yamlfile- If the Zendesk status information for an incident is not within the stored information (and it is not already resolved), the information is stored as a new incident
- If the Zendesk status information for an incident is within the stored information (but there are differences between the two), the information is stored as an updated incident
- If the update is it being resolved, the item will later be deleted from the
data/incidents.yamlfile
- If the update is it being resolved, the item will later be deleted from the
- Compares the current Zendesk status information for maintenances to that of the stored information from
data/maintenances.yamlfile- If the Zendesk status information for a maintenance is not within the stored information (and it is not already completed), the information is stored as a new maintenance
- If the Zendesk status information for a maintenance is within the stored information (but there are differences between the two), the information is stored as an updated maintenance
- If the update is it being resolved, the item will later be deleted from the
data/maintenances.yamlfile
- If the update is it being resolved, the item will later be deleted from the
- Creates a new commit to the project updating the
data/incidents.yamlanddata/maintenances.yamlfiles (if there are any new or updated items) - Makes posts to the #feed_status-zendesk-global Slack channel detailing any new or updated items
Changing the Zendesk Global system checker
Note
- This requires at least
Developeraccess to the project. - This should only be done if there is a corresponding request issue (Feature Request, Administrative, Bug, etc.). If one does not exist, you should first create one (and let it go through the standard process before working it).
To make changes to the Zendesk Global system checker, you will need to create a MR in the project repo. The exact changes being made will depend on the request itself.
After a peer reviews and approves your MR, you can merge the MR (which will have them applied on the next triggered run).
Common issues and troubleshooting
This is a living section that will have items added to it as needed.
Last modified January 21, 2026: Revamp CustSuppOps handbook (
7d49549f)
