Source: https://chiselbase.com/functions/

Firebase function logs

# Find the failed call. Read the whole story.

An email did not send. A payment timed out. Find the relevant Cloud Functions logs by function, severity, text and time, then follow one invocation in a focused desktop view.

[Download and start free](https://chiselbase.com/download/) [Compare Free and Pro](https://chiselbase.com/pricing/)

· function logs

 

Screenshot: Chiselbase Cloud Functions log viewer showing timestamped INFO, WARNING and ERROR entries for order processing, payments and inventory sync, with severity, time and text filters above the list.

An order confirmation failed among other function activity. Time, severity, function and message line up in one timeline. Real app, example data.

## From a failed request to the relevant logs.

1.  ### Start with the function that needs attention
    
    Sort the function list by errors, calls or latency. Filter by name, region or trigger, or show only functions with errors. Open its logs directly.
    
2.  ### Narrow the noise
    
    Choose a time window and severity, then search for an order ID or error message. Request and system entries have separate switches. Jump to a known timestamp when you already have one.
    
3.  ### Follow the complete invocation
    
    Choose “Show this invocation” on an entry with an execution ID. The view includes its other messages, even if your previous severity filter would have hidden them.
    

## An ERROR tells you what failed. The preceding messages explain how.

Read one call from the initial message through the retry to the failure. Chiselbase uses the execution ID already attached to your logs to isolate the invocation. Keep INFO and WARNING entries in context, inspect the payload, then switch to the related Firestore data without replacing your log tab.

Invocation grouping is available when your log entries include an execution ID.

· one invocation · order-10384

 

Screenshot: Chiselbase log view filtered to execution order-10384, showing an INFO order-received entry, a WARNING about an email retry and an ERROR for an SMTP timeout.

One invocation, three messages. The order arrives, the email provider times out and the confirmation fails. INFO and WARNING entries remain visible beside the ERROR.

## Keep the useful details. Share the evidence.

**Read the payload**

Expand a log entry to inspect its structured JSON or text payload. HTTP request entries show method, path, status and duration as separate values.

**Follow new entries**

Live tail checks for new logs while this view is active. Pause it to investigate a specific time, and load older entries as you work back through the timeline.

**Take the evidence with you**

Select the relevant entries and copy them as JSON, with metadata alone or with payloads. Attach the useful part to a bug report instead of copying the entire log stream.

**Compare runtime configuration**

Inspect environment variables and secret references, and compare function environments when configuration may explain different behavior.

[Keep the related Firestore documents open in your workspace →](https://chiselbase.com/firestore/)

## Bring your next debugging session into focus.

Connect your project, find the relevant function and narrow the logs to the request you are investigating. Google Cloud permissions and log retention still apply.

[Download and start free](https://chiselbase.com/download/) [See the full plan comparison →](https://chiselbase.com/pricing/)