> ## Documentation Index
> Fetch the complete documentation index at: https://fal.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Logs

> Explore, filter, share, and export your application logs from the dashboard.

The Logs page is the dashboard viewer for everything your app writes to `stdout` and `stderr`. It is built to cut through noise quickly: a timeline to spot error clusters, drag-to-filter to zoom into a window, and collaboration features so you and your team (or the fal team) can share and debug the same log line. For how logging works under the hood -- the different log scopes, what is captured, and how request-level logs are exposed -- see [Logging](/docs/documentation/development/logging).

<Frame>
  <iframe className="w-full aspect-video rounded-lg" srcdoc="<style>*{padding:0;margin:0;overflow:hidden}html,body{height:100%}img,span{position:absolute;width:100%;top:0;bottom:0;margin:auto}span{height:1.5em;text-align:center;font:48px/1.5 sans-serif;color:white;text-shadow:0 0 0.5em black}</style><a href='https://www.youtube.com/embed/Fw1DkM7eNPI?start=1407&end=1638&autoplay=1'><img src='/docs/docs/images/video-thumbs/logs-v2.jpg' alt='Logs - fal Serverless'><span>▶</span></a>" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />
</Frame>

## Timeline and Filtering

The logs viewer opens with a timeline histogram of log volume over time, making it easy to see when errors spiked or clustered. From there you can:

* **Drag to filter** -- select a region on the timeline to narrow all logs to that window, instead of typing exact timestamps.
* **Filter by severity** -- switch out of live mode and filter to errors (or any minimum level) to focus only on what matters.
* **Filter by identifier** -- narrow logs by runner ID, request ID, or version ID, or scope to a specific endpoint.

## Investigating a Log Line

Click into any log entry for options that make debugging faster:

* **Show in context** -- when you are filtered to error-level logs, expand a single error to see the surrounding log lines and full traceback that led to it.
* **Share link** -- copy a link that opens directly to that exact log line, at that point in time and with the same filter applied, so a teammate lands on precisely what you are looking at.

## Collaborating and Exporting

Debugging production apps is often a team effort, so the Logs page makes it easy to move logs out of the dashboard:

* **Copy multiple lines** -- bulk-select log lines and copy them (as CSV) to paste into Slack for a teammate or into an agent for analysis.
* **Export as CSV** -- export the full, filtered set of logs at once.

## Related

* [Logging](/docs/documentation/development/logging) -- log scopes, what is captured, and request vs runner logs
* [Runner Analytics](/docs/documentation/serverless/observability/runner-analytics) -- logs filtered to a single runner, alongside telemetry and cold start stages
* [Log Drains](/docs/documentation/serverless/observability/log-drains) -- forward logs to external services (Datadog, Splunk, or any HTTP endpoint) in real time
