chore(demo): monitor GitHub/Cloudflare/npm via the statuspage adapter#36
Draft
amondnet wants to merge 1 commit into
Draft
chore(demo): monitor GitHub/Cloudflare/npm via the statuspage adapter#36amondnet wants to merge 1 commit into
amondnet wants to merge 1 commit into
Conversation
The hosted demo pinged api.github.com / cloudflare.com / npm as plain http checks. GitHub, Cloudflare and npm all publish an Atlassian Statuspage, so mirror their own published verdict via check: statuspage instead — a better showcase of the adapter with real component-level data. Keep one plain http check (1.1.1.1) for contrast.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates status.config.yml to use the Statuspage adapter for GitHub, Cloudflare, and npm, querying their official status pages instead of performing naive HTTP reachability pings. A single plain HTTP check for Cloudflare DNS is kept as a direct reachability probe. There are no review comments to evaluate, and no further feedback is required.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Switch the hosted demo (
demo.statusbeam.dev) from plainhttpreachability pings to thestatuspageadapter for the vendors that publish an Atlassian Statuspage — a better showcase of the adapter with real, component-level data.httpapi.github.comstatuspagewww.githubstatus.comhttpcloudflare.comstatuspagewww.cloudflarestatus.comhttpregistry.npmjs.orgstatuspagestatus.npmjs.org (component: Package installation)http1.1.1.1http1.1.1.1 (kept, for contrast)Keeping one
httpcheck means the demo shows both check kinds side by side.Why
The demo exists to show off this product; mirroring each vendor's own published verdict is more on-message than a naive reachability ping, and surfaces component-level status.
Verification
Ran the real
checkSiteagainst the live pages via the core package:Config also validated through
parseConfig(all slugs derive correctly; the npmcomponentresolves against the live page).Notes
Related issue
None.
Summary by cubic
Switch the hosted demo (
demo.statusbeam.dev) from plainhttppings to thestatuspageadapter for GitHub, Cloudflare, and npm to show real, component-level status. Keep onehttpcheck (Cloudflare DNS at 1.1.1.1) for contrast.statuspage: https://www.githubstatus.comstatuspage: https://www.cloudflarestatus.comstatuspage: https://status.npmjs.org withcomponent: Package installationhttp: https://1.1.1.1Written for commit 40750a5. Summary will update on new commits.