Metrics
Monitor application behavior with aggregated time-series data.
Metrics summarize application and platform behavior over time on the project Observability page.
Default charts
Typical charts include:
Traffic
- Edge Requests: request volume and error rates
- Edge Bandwidth: incoming and outgoing bytes
Functions
- Function Starts: cold versus warm starts
- Functions: invocation and error series
- Compute: total compute duration
Runtime Cache
- Runtime Cache operations when the project uses runtime cache APIs
Time windows and buckets
Select a preset window such as 6 hours, 12 hours, 24 hours, or 7 days.
Aggregation buckets are typically:
- 5 minutes for windows up to 24 hours
- 60 minutes for longer windows
Custom queries
Open Observability → Query (or the project query view) to build charts from supported metrics such as:
- Edge requests
- Duration
- Bandwidth / FDT fields
- Route cache and route bandwidth
- Function metrics
Supported aggregations include count, sum, min, max, average, and percentiles such as p75, p90, p95, and p99 where the metric allows them.
Custom query metrics are platform-defined fields and aggregations, not arbitrary customer-defined metric names emitted from application code.
How to use metrics after a deploy
- Open Observability for the hours after the release.
- Compare error rate, latency/compute, cold starts, and bandwidth to the prior window.
- When a series moves, open Logs for the same time range.
- Inspect request detail and Trace for examples.
Deployment overlay markers on charts are not a separate product feature today. Use time range and deployment ID filters instead.