-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public monitoring/status dashboard #1546
Comments
Assuming we're just trying to show what the average user cares about, a simple graph of connectivity between Bsky to Fedi and Fedi to Bsky, and the number of processes per second or minute would be sufficient. |
Honestly I think the most important things are downtime (ie. simple status window saying things like: bluesky refusing connections) and backlog size/time (what's the age of the oldest post in the backlog and how many items are in there). Should be much easier than a rate counter to implement. |
The goal here is very different than identifying or communicating about the recent outage for bridging into Bluesky. We're working on that in bluesky-social/atproto#3094 (reply in thread) |
I mention that just as an example, a good status page has places for notices so people can check just a single page. I was just saying it'd be something like: [notice field] Bluesky-to-AP: [number of posts in queue] / [age of oldest] (assuming separate queues, if a single queue then just one line) And if you want to be fancy about it a nice little graph of both. |
I've had a good monitoring dashboard for a while, #1060 (comment) , but it's built on Google Cloud Monitoring, which sadly doesn't support public visibility, https://issuetracker.google.com/issues/354101899 . Maybe someday!
The text was updated successfully, but these errors were encountered: