On this page

Reports and charts

Charts of a project over time: database connections, pooler, primary and replica traffic, replication lag, database size, API requests, realtime clients, CPU and memory.

Every project has a Reports page (project sidebar → Reports) and a 24-hour chart strip on its overview. Pick 1h, 24h, 7d or 30d; on 1h the charts refresh every 30 seconds. Hover a chart for exact values, or press Table to read the numbers.

#What the charts show

ChartWhat it measures
Database connectionsClient connections to the primary database by state: active, idle in transaction, idle.
Connections by sourceYour app (through the connection pooler, including direct connections on port 5432) and the project services: REST API, Auth, Storage, Realtime. Kept for 24 hours.
Pooler clientsClient connections to the pooler and clients waiting for a server connection, with your plan’s pooler limit as a dashed line.
Pooler server connections in useDatabase connections the pooler is using, against the pool size.
API requests per nodeRequests per second on the primary and on each read replica. Reads are answered by the replica nearest the user.
Replication lagHow far each read replica is behind the primary.
Connections per nodeClient connections on the primary and on each read replica (only with replicas).
Database sizeSize of the database against the size included in your plan.
Transactions, cache hit rateCommitted and rolled-back transactions per second; share of reads answered from memory.
API requests, server errorsAll API requests per second against your rate limit, and the share answered with a 5xx error.
Realtime clientsConcurrent realtime connections against your plan.
CPU, memoryThe project’s own services (API, Auth, Storage).

#How often, how long

Values are sampled every minute. StitchDB keeps 1 hour at 1-minute detail, 24 hours at 10 minutes, 7 days at 2 hours and 13 months at 1 day; older detail rolls up into the coarser views. API requests are counted every 5 minutes. A gap in a chart means no sample was taken (for example while the project was paused).

#From code

Management API
curl 'https://stitchdb.com/platform/v1/projects/<project-ref>/metrics?range=24h' \
  -H "Authorization: Bearer $STITCHDB_TOKEN"

Works with a personal or organization access token with read access. The response lists each node serving the project (primary and replicas) with its points, and your plan’s limits.

Was this helpful?