Skip to content

README.md

Latest commit

 

History

History
76 lines (52 loc) · 15.5 KB

README.md

File metadata and controls

76 lines (52 loc) · 15.5 KB

📈 Live Status: 🟧 Partial outage

This repository contains the open-source uptime monitor and status page for FAIR Project, powered by Upptime.

Uptime CI Response Time CI Graphs CI Static Site CI Summary CI

URL Status History Response Time Uptime
FAIR 🟩 Up fair.yml
Response time graph 156ms
Response time 353
24-hour response time 248
7-day response time 156
30-day response time 173
1-year response time 353
100.00%All-time uptime 99.49%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 99.49%
FAIR API 🟩 Up fair-api.yml
Response time graph 182ms
Response time 654
24-hour response time 161
7-day response time 182
30-day response time 651
1-year response time 654
100.00%All-time uptime 99.03%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 98.48%
1-year uptime 99.03%
AspireCloud.net (Production) 🟩 Up aspire-cloud-net-production.yml
Response time graph 267ms
Response time 276
24-hour response time 169
7-day response time 267
30-day response time 287
1-year response time 276
100.00%All-time uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%
AspireCloud.io (Staging) 🟥 Down aspire-cloud-io-staging.yml
Response time graph 0ms
Response time 0
24-hour response time 0
7-day response time 0
30-day response time 0
1-year response time 0
0.00%All-time uptime 0.00%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 0.00%
1-year uptime 0.00%

🛠️ Configuration

This more or less runs automated without the need for intervention.

  • Basic config, including monitored sites, is in .uptimerc.yml
  • CSS is configured in the assets/fair-theme.css file.
  • Custom log is assets/logo.svg (note that the logo is a placeholder for now)

To make updates, create a branch from master (no we cannot rename it, as it's dependant on the parent template), make your changes, and merge back into master.

DNS

To customize the URL as status.fair.pm

On Github:

  1. Click on SETTINGS for this repository
  2. Click on Pages on the left hand menu
  3. Under Custom Domain, put in status.fair.pm and click save
  4. Update the .upptimerc.yml file to use CNAME=status.fair.pm
  5. Push the code to production

On AWS Route 53

  1. Log in to AWS: Open the AWS Management Console and navigate to the Route 53 service.
  2. Select your Hosted Zone: Click on Hosted zones and select the domain fair.pm.
  3. Create a new record: Click the Create record button.
  4. Configure the record:
  • Record name: Enter status.
  • Record type: Choose CNAME - Routes traffic to another domain name and to some AWS resources.
  • Value: Enter fairpm.github.io. Important: Do not include the /status part of the URL. The CNAME record should point to the root GitHub Pages domain.
  • TTL (Seconds): You can leave this at the default setting.
  1. Save the record: Click the Create records button.

After you've completed these steps, it may take some time for the DNS changes to propagate, though it is often quite fast.

🚨 Incidents, Outages, and Planned Maintenance

If the monitored sites (see .uptimerc.yml) go down, a new issue will be opened in Github and Slack will be alerted. If the site comes back up, the issue will be closed.

When a specified endpoint goes down, Upptime automatically opens a new issue in your GitHub repository. You can use this issue to add more information about the outage, such as whether you are investigating, what caused the downtime, etc.

We have a custom issue template for "Maintenance Event" to be used for any planned outages.

We also automatically alert Slack.

📄 License