# Public simplified system dashboard

**URL:** https://forum.meet.coop/t/public-simplified-system-dashboard/1522
**Category:** Infrastructuring
**Created:** [30 October 2024 13:54 UTC](https://forum.meet.coop/t/public-simplified-system-dashboard/1522 "2024-10-30T13:54:17Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![jonr](https://forum.meet.coop/user_avatar/forum.meet.coop/jonr/32/1083_2.png) [@jonr](https://forum.meet.coop/u/jonr)
#### Post date: [30 October 2024 13:54 UTC](https://forum.meet.coop/t/public-simplified-system-dashboard/1522/1 "2024-10-30T13:54:17Z")

</div>

Hi [Meet.Coop](http://Meet.Coop)!

I’m part of a conversation series that is going to take place during the next half a year on [meet.coop](http://meet.coop) BBB. We’ve found occassional breakups with medium loads (atm 12 ppl.).

Would it seem feasible to provide a simple publish dashboard showing the abstracted metrics of system load, which could help identification of local or remote bottlenecks?

Right now, for example,

> as a participant in a call for whom the connection lags at times, I need to have a way to learn about the overall system health, in order to find out if the problems are from my connection or from the server.

`status.meet.coop` comes to mind.