Skip to main content
Once your app is deployed and serving traffic, you need visibility into how it is performing. fal provides three interfaces for observability, each suited to different workflows. The dashboard gives you visual, real-time insight into requests, runners, and errors. The CLI lets you check runner states and stream logs from your terminal. And the programmatic integrations (Prometheus metrics, log drains, Slack notifications) let you pipe fal’s data into your existing monitoring stack. Understanding which interface to use for which task saves you from digging through the wrong tool. The dashboard is best for investigating specific issues and getting a quick overview. The CLI is best for quick operational checks and scripting. The integrations are best for production alerting, long-term metrics storage, and centralized logging.

​
Dashboard

The fal dashboard is the primary interface for visual monitoring. It provides several views depending on what you need to understand. App Analytics shows request volume, latency, runner counts, and queue depth for each deployed app. Use it to understand traffic patterns, identify slow endpoints, and verify that scaling is working correctly. The Requests tab shows individual request history with status, duration, and logs. The Runners tab shows runner lifecycle events and state transitions. Error Analytics breaks down failures by error type, status code, and time. Use it to spot error spikes, identify recurring failure patterns, and understand which errors are transient vs systemic. App Events tracks deployment events, configuration changes, and runner lifecycle events. Use it to correlate performance changes with deployments (e.g., “latency increased right after this deploy”). Logs streams runner logs in real-time and lets you filter by runner ID, request ID, version, and source. For understanding how request-level logs work, see Logging.

App Analytics

Request metrics, runner states, and per-app performance

Error Analytics

Error rates, patterns, and failure breakdown

App Events

Deployment, config, and runner lifecycle events

​
CLI

The fal CLI provides quick access to runner states, logs, and queue status from your terminal. This is useful for operational checks, scripting, and CI pipelines. 
# Runner monitoring
fal runners list                        # all runners with current states
fal runners list --state idle           # filter by state
fal runners list --since "1h"           # view history
fal runners logs <runner-id>            # stream logs from a runner

# Queue monitoring
fal queue size my-app                   # current queue depth
fal queue flush my-app                  # clear stuck requests

# App management
fal apps list                           # all deployed apps
fal apps runners my-app                 # runners for a specific app
fal apps scale my-app                   # view/update scaling config
See the CLI reference for fal runners, fal queue, and fal apps.

​
Programmatic Integrations

For production monitoring, you can pipe fal’s data into your existing observability stack. This gives you long-term retention, custom dashboards, and alerting that the built-in dashboard does not provide. Prometheus Metrics — fal exposes a Prometheus-compatible metrics endpoint that you can scrape with Grafana, Datadog, or any Prometheus-compatible tool. Available metrics include runner counts, queue depth, concurrent requests, request throughput, and latency buckets. Log Drains — forward all runner logs to an external service (Datadog, Splunk, or any HTTP endpoint) in real-time via NDJSON over HTTPS. Logs include request IDs, timestamps, and structured metadata for correlation. Slack Notifications — receive alerts in Slack when runners fail to start, deployments complete, or configuration changes occur.

Exporting Metrics

Prometheus endpoint, Grafana setup, and Datadog integration

Log Drains

Forward logs to external services in real-time

Slack Notifications

Alert on deployments, failures, and config changes