Open yangwao opened 2 years ago
This is like great candidate https://calibreapp.com/
Free public status page https://www.atlassian.com/software/statuspage/pricing?tab=public
hello, I will try to create this status page
oh, just realized this is hackathon
tag
two submissions from me:
Repo: https://github.com/preschian/kodadot-status URL: https://preschian.github.io/kodadot-status/
Pros:
Cons:
URL: https://kodadot.betteruptime.com/
Pros:
Cons:
I'm impressed!
I guess thinking for the easier check we should have one list of all URLs we need to check for a client to work?
Do we have a global list of endpoints we are using? If not, let's create one and we can merge it with #1492
I've noticed we should add there Estuary endpoint. Is there anything missing from list ?
π Hello, can we extend this with bsx & moon endpoints? as I need to know more on the servers uptime.
I like betteruptime design but it look like it miss incident features
If we're going to use an open source solution (we can lookup https://github.com/ivbeg/awesome-status-pages), I would add the repo to kodadot org and link it in doc too
bsx & moon endpoints ? yes for both
plus we've added nft.storage which is currently passing through workers but would be good anyway, but bet it should be stable.
updated remaining endpoints here https://github.com/preschian/kodadot-status/pull/97
what is the moon endpoint? I couldn't find from here https://github.com/kodadot/nft-gallery/blob/main/utils/constants.ts
wow, https://preschian.github.io/kodadot-status/ beautiful!
what is the moon endpoint? I couldn't find from here
main
/utils/constants.ts
if we are good to go, I think it's better to move the repo under https://github.com/kodadot
I just realized og-image on vercel had a couple of downtimes in this three days better to move og-image repo under kodadot also
if we are good to go, I think it's better to move the repo under @kodadot
let's proceed :)
better to move og-image repo under kodadot also
that's would be great; I can reach out to Andrey and probably would need to redeploy on vercel?
let's proceed :)
ok, let me try to move the repository
that's would be great; I can reach out to Andrey and probably would need to redeploy on vercel?
It would be great if the output of the URL were still the same
unable to move the repository
You donβt have the permission to create public repositories on kodadot
handovering from Discord from Vik
Hey @Contributing Developer,
I just released a small API to check if our indexers are running.
Currently it has just two routes:
- /list - get list of all indexers
- /status/:id - status of the indexer
the API is awailable on the route https://squiki.kodadot.workers.dev/
Example
to get a status of rubick just call:
https://squiki.kodadot.workers.dev/status/rubick
I hope it can help you to debug things :pepemeow:
Example to get a status of rubick just call: https://squiki.kodadot.workers.dev/status/rubick
hooo, I like that endpoint status π
hhmm, for next, how to update that deploymentURL automatically in the status repo π€
I just want to confirm, what is the status code if deploymentUrl was down? does the https://squiki.kodadot.workers.dev/status/rubick will throw a non-200 status, or will it respond with 200, but the versions
from JSON response will change to non AVAILABLE
?
For particular reason to be aware if we are up or not would be great to have handsome endpoints to see what's needed to have seamless working with users
spec
We should be able monitoring endpoints and route on minute basis, hope that's enough using serverless functions
Then we could measure amount of time to resolve particular queries for routes
stack
@roiLeo suggested https://github.com/juliomrqz/statusfy
probably it could be written as serverless function, we have some spare capacity on Netlify but for the reason, later it should be running outside Netlify to verify if there is everything ok