Observability
Three records of a running application, covering what your code printed, what the platform served, and what it consumed.
A running deployment leaves three trails. Your code's output and one row per served request sit together in the console under Logs, scoped to an environment. Metered totals sit under Usage, scoped to the whole organization.
Runtime logs
Standard output and standard error from your Functions. Start here when your code did something you did not expect.
Request logsStatus, timing, cache outcome and sanitized headers for every request. Start here when the response was wrong before your code ran, or never ran at all.
UsageMetered quantities per metric and per application, and why spend appears when it does.