How we built Status Page

GitLab has developed a Status Page tool to enhance incident management for its internal team and customers, available to GitLab Ultimate users with a frontend accessible to all. The tool aims to streamline incident updates by eliminating the need for responders to switch between tools and manage information duplication, addressing the drawbacks of the previous system where updates were manually published by engineers every 15 minutes. The Status Page allows for controlled visibility of incident updates to protect sensitive information, and it displays comprehensive data from GitLab incident descriptions and comments. Built with VueJS for the frontend and hosted separately under an MIT license, the Status Page utilizes a background job to convert incident issues into JSON, which is then published, supporting storage on Amazon S3 to ensure availability even if Google Cloud experiences downtime. The development process, driven by GitLab's Monitor:Health team, involved a Spike exercise to determine the best implementation approach, leading to the creation of a stand-alone application that integrates seamlessly with GitLab's ecosystem.

No tracked trend matches for this post yet.