Each app’s dashboard pages answer the two questions you actually ask in production: what is this app doing right now, and who exactly is connected.
App overview
The overview tab shows the live picture and the month so far:
| Live | Monthly |
|---|---|
| Active connections | Total messages |
| Active channels | Peak connections and channels |
| Messages per second | Bandwidth and current spend |
Live numbers are aggregated from every edge server and reflect roughly the last 30 seconds. The monthly numbers are the same accounting the bill uses, per Usage and billing.
Connection inspector
The connections tab lists live connections on demand: each one’s connectionId, clientId, attached channels, and connect time. Nothing is collected until you open the page. The dashboard asks the edge servers at that moment, which means there’s no stored connection log to leak or to pay for, and the page shows up to 250 connections at a time.
The same tab lists active channels with their subscriber counts, so “which channel is busy right now” is one click.
Monitoring from your own code
The dashboard views are session-authenticated and have no public API. What your code can read with normal credentials:
- Presence gives you who’s on a channel, over the SDK or REST.
- Channel occupancy is available through the Pusher-compatible HTTP API’s channel endpoint when you need a subscriber count programmatically.
- Connection state for your own clients is the
connection.onAPI in Connections.
For alerting on volume, the budget email alerts in Usage and billing fire at 50%, 90%, and 100% of a monthly budget you set.