Observability
Metrics and usage
Mesh measures what each service actually consumes: CPU, memory, volume space, and public egress. The same measurements drive the service charts, the usage reports, and your bill.
What is measured
| Meter | Measured as |
|---|---|
| CPU | CPU time used, in vCPU |
| Memory | Memory in use, including page cache |
| Volume | Disk space in use on the volume |
| Public egress | Bytes your service sends to the internet |
Private traffic between services is free. A sleeping serverless service uses no CPU, memory, or egress.
Service metrics
Open a service and go to Metrics for CPU, memory, and egress over time. Egress is split into traffic sent directly and traffic answered through the edge.
Usage reports
The workspace Usage page shows usage and estimated cost by project for a time range. Open a project to break it down by service and volume. When measurements are missing for a while, the report shows the gap instead of guessing.
Through the API:
curl "https://mesh.example.com/v1/projects/$PROJECT_ID/usage?start_time=2026-11-01T00:00:00Z&end_time=2026-11-07T00:00:00Z&resolution=USAGE_RESOLUTION_DAY" \
-H "Authorization: Bearer $MESH_TOKEN"Prices and plans are in Plans and billing.