From 639ef9fd217ca4ae5c1d538bd1726636a73b0fa6 Mon Sep 17 00:00:00 2001 From: Upptime Bot <73812536+upptime-bot@users.noreply.github.com> Date: Wed, 3 Jan 2024 03:35:32 +0000 Subject: [PATCH] :pencil: Update summary in README [skip ci] [upptime] --- README.md | 102 ++++++++---------------------------------------------- 1 file changed, 14 insertions(+), 88 deletions(-) diff --git a/README.md b/README.md index 1335a3e75..b5be2d5e1 100644 --- a/README.md +++ b/README.md @@ -1,22 +1,14 @@ -# [![Upptime](https://raw.githubusercontent.com/upptime/upptime.js.org/master/static/img/logo.svg)](https://upptime.js.org) +# [📈 Live Status](https://status.skkuding.dev): **🟧 Partial outage** - +This repository contains the open-source uptime monitor and status page for [SKKUDING](https://skkuding.dev), powered by [Upptime](https://github.com/upptime/upptime). -**Upptime** (https://upptime.js.org) is the open-source uptime monitor and status page, powered entirely by GitHub Actions, Issues, and Pages. It's made with 💚 by [Anand Chowdhary](https://anandchowdhary.com), supported by [Pabio](https://pabio.com). +[![Uptime CI](https://github.com/skkuding/uptime-monitor/workflows/Uptime%20CI/badge.svg)](https://github.com/skkuding/uptime-monitor/actions?query=workflow%3A%22Uptime+CI%22) +[![Response Time CI](https://github.com/skkuding/uptime-monitor/workflows/Response%20Time%20CI/badge.svg)](https://github.com/skkuding/uptime-monitor/actions?query=workflow%3A%22Response+Time+CI%22) +[![Graphs CI](https://github.com/skkuding/uptime-monitor/workflows/Graphs%20CI/badge.svg)](https://github.com/skkuding/uptime-monitor/actions?query=workflow%3A%22Graphs+CI%22) +[![Static Site CI](https://github.com/skkuding/uptime-monitor/workflows/Static%20Site%20CI/badge.svg)](https://github.com/skkuding/uptime-monitor/actions?query=workflow%3A%22Static+Site+CI%22) +[![Summary CI](https://github.com/skkuding/uptime-monitor/workflows/Summary%20CI/badge.svg)](https://github.com/skkuding/uptime-monitor/actions?query=workflow%3A%22Summary+CI%22) -> I find Upptime an incredible clever usage of \[GitHub Actions]. You essentially get a free configurable uptime monitor for whatever you want. – [CSS Tricks](https://css-tricks.com/upptime/) - -Upptime is used by [**1,000+**](https://github.com/topics/upptime) people and teams to ensure they know when their endpoints go down. - - - -[![Uptime CI](https://github.com/upptime/upptime/workflows/Uptime%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Uptime+CI%22) -[![Response Time CI](https://github.com/upptime/upptime/workflows/Response%20Time%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Response+Time+CI%22) -[![Graphs CI](https://github.com/upptime/upptime/workflows/Graphs%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Graphs+CI%22) -[![Static Site CI](https://github.com/upptime/upptime/workflows/Static%20Site%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Static+Site+CI%22) -[![Summary CI](https://github.com/upptime/upptime/workflows/Summary%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Summary+CI%22) - -## [📈 Live Status](https://demo.upptime.js.org): **🟧 Partial outage** +With [Upptime](https://upptime.js.org), you can get your own unlimited and free uptime monitor and status page, powered entirely by a GitHub repository. We use [Issues](https://github.com/skkuding/uptime-monitor/issues) as incident reports, [Actions](https://github.com/skkuding/uptime-monitor/actions) as uptime monitors, and [Pages](https://status.skkuding.dev) for the status page. @@ -24,83 +16,17 @@ Upptime is used by [**1,000+**](https://github.com/topics/upptime) people and te | URL | Status | History | Response Time | Uptime | | --- | ------ | ------- | ------------- | ------ | -| [Google](https://www.google.com) | 🟩 Up | [google.yml](https://github.com/upptime/upptime/commits/HEAD/history/google.yml) |
Response time graph 71ms
Response time 107
24-hour response time 76
7-day response time 71
30-day response time 88
1-year response time 108
|
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 99.99%
-| [Wikipedia](https://en.wikipedia.org) | 🟩 Up | [wikipedia.yml](https://github.com/upptime/upptime/commits/HEAD/history/wikipedia.yml) |
Response time graph 288ms
Response time 244
24-hour response time 360
7-day response time 288
30-day response time 224
1-year response time 257
|
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%
-| [Hacker News](https://news.ycombinator.com) | 🟩 Up | [hacker-news.yml](https://github.com/upptime/upptime/commits/HEAD/history/hacker-news.yml) |
Response time graph 367ms
Response time 375
24-hour response time 355
7-day response time 367
30-day response time 1319
1-year response time 400
|
100.00%All-time uptime 98.43%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 99.61%
1-year uptime 99.93%
-| [Test Broken Site](https://thissitedoesnotexist.koj.co) | 🟥 Down | [test-broken-site.yml](https://github.com/upptime/upptime/commits/HEAD/history/test-broken-site.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%
+| [Google](https://www.google.com) | 🟩 Up | [google.yml](https://github.com/skkuding/uptime-monitor/commits/HEAD/history/google.yml) |
Response time graph 80ms
Response time 80
24-hour response time 80
7-day response time 80
30-day response time 80
1-year response time 80
|
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%
+| [Wikipedia](https://en.wikipedia.org) | 🟩 Up | [wikipedia.yml](https://github.com/skkuding/uptime-monitor/commits/HEAD/history/wikipedia.yml) |
Response time graph 70ms
Response time 70
24-hour response time 70
7-day response time 70
30-day response time 70
1-year response time 70
|
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%
+| [Hacker News](https://news.ycombinator.com) | 🟩 Up | [hacker-news.yml](https://github.com/skkuding/uptime-monitor/commits/HEAD/history/hacker-news.yml) |
Response time graph 103ms
Response time 103
24-hour response time 103
7-day response time 103
30-day response time 103
1-year response time 103
|
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%
+| [Test Broken Site](https://thissitedoesnotexist.koj.co) | 🟥 Down | [test-broken-site.yml](https://github.com/skkuding/uptime-monitor/commits/HEAD/history/test-broken-site.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
|
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%
- - -## ⭐ How it works - -- GitHub Actions is used as an uptime monitor - - Every 5 minutes, a workflow visits your website to make sure it's up - - Response time is recorded every 6 hours and committed to git - - Graphs of response time are generated every day -- GitHub Issues is used for incident reports - - An issue is opened if an endpoint is down - - People from your team are assigned to the issue - - Incidents reports are posted as issue comments - - Issues are locked so non-members cannot comment on them - - Issues are closed automatically when your site comes back up - - Slack notifications are sent on updates -- GitHub Pages is used for the status website - - A simple, beautiful, and accessible PWA is generated - - Built with Svelte and Sapper - - Fetches data from this repository using the GitHub API - -_Upptime is not affiliated to or endorsed by GitHub._ - -[![Screenshot of status website](https://raw.githubusercontent.com/upptime/upptime.js.org/master/static/img/screenshot-status.png)](https://upptime.js.org) - -## 👩‍💻 [Documentation](https://upptime.js.org) - -1. [How it works](https://upptime.js.org/docs) -1. [Getting started](https://upptime.js.org/docs/get-started) -1. [Configuration](https://upptime.js.org/docs/configuration) -1. [Triggers](https://upptime.js.org/docs/triggers) -1. [Notifications](https://upptime.js.org/docs/notifications) -1. [Badges](https://upptime.js.org/docs/badges) -1. [Packages](https://upptime.js.org/docs/packages) -1. [Contributing](https://upptime.js.org/docs/contributing) -1. [Frequently Asked Questions](https://upptime.js.org/docs/faq) - -### Concepts - -#### Issues as incidents - -When the GitHub Actions workflow detects that one of your URLs is down, it automatically opens a GitHub issue ([example issue #67](https://github.com/upptime/upptime/issues/67)). You can add incident reports to this issue by adding comments. When your site comes back up, the issue will be closed automatically as well. - - - - - - -
- Screenshot of GitHub issue - - Screenshot of incident page -
- -#### Commits for response time - -Four times per day, another workflow runs and records the response time of your websites. This data is committed to GitHub, so it's available in the commit history of each file ([example commit history](https://github.com/koj-co/upptime/commits/master/history/wikipedia.yml)). Then, the GitHub API is used to graph the response time history of each endpoint and to track when a site went down. - - - - - - -
- Screenshot of GitHub commits - - Screenshot of live status -
- +[**Visit our status website →**](https://status.skkuding.dev) ## 📄 License +- Powered by: [Upptime](https://github.com/upptime/upptime) - Code: [MIT](./LICENSE) © [Anand Chowdhary](https://anandchowdhary.com), supported by [Pabio](https://pabio.com) - Data in the `./history` directory: [Open Database License](https://opendatacommons.org/licenses/odbl/1-0/)