Observability
Traffic, errors, latency and cold starts per function, plus the build output for every version.
Traffic stats
The edge serves or proxies every request on both paths — static and container — and reports what it saw. Per function you get:
| Requests | Total, including static. |
| 4xx / 5xx | Counted by response status. |
| Cold starts | How many requests waited for an instance to start. |
| p50 / p95 | Response latency in milliseconds. |
Cold starts are counted from the platform's own answer, not inferred from latency — inferring them would be wrong exactly when the platform is busy, which is when you would be looking.
Resolution and retention
Counters are stored in 5-minute buckets and kept for 14 days. A request for a finer step is raised to the storage resolution rather than refused, and a long range is coarsened so a chart comes back with at most 500 points.
The default range is the last 24 hours. Empty steps are returned as zeros rather than omitted — a chart with gaps where nothing happened lies about the shape of the traffic.
About the percentiles
Latency is bucketed into a fixed histogram — 25, 50, 100, 250, 500, 1000, 2500 and 10000 ms — and percentiles are interpolated within the bucket that contains the target rank. This is crude and honest: enough to tell "healthy" from "not", not a substitute for a tracing system.
Counters are flushed from the edge every few seconds as deltas, so an edge restart loses at most one interval rather than resetting a total.
Build logs
Every version's build output is captured and readable from its deploy, during the build and afterwards. A failed build's log is the whole error message, so it is kept rather than streamed and forgotten.
A static version builds nothing, and reads back as an empty log rather than an error.
What is not available
Application logs are not available yet. Your process's stdout and stderr at
runtime are not readable from the console or the API — the capability does not
exist on the platform side, so the server answers unimplemented and the
console renders the tab as awaiting support rather than as broken. Build output
is the only log surface today.
Also not available yet: custom domains, and per-request tracing.