Skip to main content
Edge Compute exposes two log types through the same CLI command and API endpoint:

​
Runtime logs

Runtime logs are the default:
Each line prints as [timestamp] [level] message, oldest first. The level is best-effort and can be inaccurate on stack traces; a multi-line error arrives as several separate entries.

​
Invocation logs

Use --type invocations for platform-generated request records:
Invocation logs report traffic even when your code never calls console.log. Each record includes request metadata such as timestamp, HTTP method, path, status code, duration, request and response size, and serving region when available. --since, --last, and --json work the same way for both log types. --since defaults to 1h and is capped at 24h; --last defaults to 50 and is capped at 250. Results are returned oldest first. The API exposes both streams through GET /v2/compute/funcs/{id}/logs with type=runtime or type=invocations. See the API Reference.

​
Emit custom events to a sink you run

Runtime and invocation logs cover platform-retained logs. If you also need application-specific structured events in your own system, send them over HTTPS to a collector you control. Store the collector credential as a secret, never in code. Declare the secret in func.toml:
Keep telemetry off the response’s critical path, apply an outbound timeout, and do not let a failed telemetry request fail the function response. Log metadata rather than sensitive request payloads. See the CLI reference for the full command reference.