Vigor uses issues to display incidents and labels for severity. Technically, Vigor is the static client-side status page built on React using GitHub Issues for Component and Incident reporting with live updating using the GitHub API.
- Easy setup
- Show status of your services using Components
- Report Incidents
- Markdown support
- Component and Incident templates
- Easy integration with services and monitoring
- Live updating status page
- Hosting on GitHub Pages or other hosting providers
- Use Zapier Triggers to update the status page
- Run
npm run deploythis will build the React project and deploy it to thegh-pagesbranch - Finally make sure GitHub Pages option in your GitHub repository settings is set to use the
gh-pagesbranch
You may also want to configure issue templates for your repository which will act as Component and Incident templates. Including the status label in an issue template will allow unauthorised GitHub users to update the status page, this should be added when creating the issue
Updating is important to get the latest features and patches
- This guide should bring you through the steps of syncing your forked version of this repository. Ensure you have backed up your
.envconfiguration file as this may be overwritten, you will need to make sure you include the env variables from the latest version
Customise your status page - ensure all required options are entered and any unused optional options are set blank, ie REACT_APP_MANIFEST=
REACT_APP_MANIFEST(optional) - Determines the manifest url in the built HTML fileREACT_APP_TITLE(required) - Determines the<title>tag in the built HTML file with suffixStatusREACT_APP_DESCRIPTION(optional) - Determines the description<meta>tag in the built HTML fileREACT_APP_LOGO(optional) - Accepts an image URL and is used in the status page headerREACT_APP_NAME(optional) - Used in the status page header when noREACT_APP_LOGOis provided. This will be used in the img alt attribute if a logo is providedREACT_APP_REPOSITORY(required) - GitHubusername/repositorythat Components and Incidents will be fetched from, ievedilink/vigor
In depth overview of the functionality
- The main status bar logic is as follows: < 70% Components
operational= "Some systems are experiencing issues", more than 0 Componentsmajor outage= "Some systems are experiencing a major outage". Otherwise, "All Systems Operational" - A
Componenteach display a current status. To create a Component add tagsstatus,componentand a tag for the current status:operational,performance issues,partial outageormajor outage(if an issue only hasissue statusandcomponentit will be listed asUnknown) to a GitHub Issue. - A
Incidentwill show in the Incidents section as eitherActiveorCloseddepending whether on the GitHub Issue is Open or Closed. To create an Incident add tagsstatusandincidentto a GitHub Issue. - Vigor uses the GitHub API v3 which has a rate limit of 60 requests per hour for unauthenticated requests. Vigor will fetch 15 times per hour, sending 2 requests per fetch / 30 requests per hour (excluding reload button)