Console
View real-time engine and application logs with filtering, color-coded categories, and export capabilities.
This is the “Logs” page
In the project sidebar, this view is labeled Logs (under the Observe group) and lives at the /console route. For app-level error tracking specifically, see the dedicated Errors page.
Overview
The Console provides a live view of your project's engine logs. Every action in your project — endpoint calls, database queries, auth events, AI operations — generates log entries that appear here in real time.
The console supports live streaming, multiple filtering modes, and export options to help you debug issues and monitor your application in production.
Live Mode
Toggle Live mode to enable automatic log polling. When active, the console auto-scrolls to show the latest entries as they arrive.
You can configure the polling interval based on your needs:
| Interval | Use case |
|---|---|
2s | Active debugging — highest refresh rate |
4s | Default — balanced performance and freshness |
10s | Moderate monitoring — lower resource usage |
30s | Background monitoring — minimal overhead |
Pause live mode to inspect specific log entries without the view scrolling away. A "scroll to bottom" button appears when you scroll up.
Filtering
The console offers two filtering dimensions that can be combined:
By Scope
| Scope | Shows |
|---|---|
| User | User-triggered activity only (endpoint calls, auth events, storage operations) |
| All | Full debug output including internal engine logs, health checks, and system events |
By Log Level
| Filter | Levels shown |
|---|---|
| All | DEBUG, INFO, WARN, ERROR |
| Warnings + Errors | WARN, ERROR |
| Errors only | ERROR |
Log Categories
Every log entry is tagged with a category and color-coded for quick visual identification. This makes it easy to scan through large volumes of logs and find relevant entries:
| Tag | Color | Source |
|---|---|---|
[ERROR] | Red | Application errors and unhandled exceptions |
[WARN] | Yellow | Deprecation notices, near-limit warnings |
[ENDPOINT] | Blue | API endpoint execution (method, path, status) |
[WORKFLOW] | Purple | Flow editor node execution steps |
[AUTH] | Orange | Login, logout, token refresh, provider events |
[AI] | Emerald | LLM calls, agent execution, MCP tool use |
[DATABASE] | Sky | SQL queries, table operations, migrations |
[STORAGE] | Amber | File uploads, downloads, bucket operations |
[HTTP] | Cyan | Outbound HTTP requests (HTTP Request node, integration nodes) |
[RATE_LIMIT] | Red | Rate limiting events and throttled requests |
[INFO] | Blue | General informational messages |
[DEBUG] | Gray | Verbose debug output (only in All scope) |
Reading Log Entries
Each log entry follows a consistent format:
[2024-03-15 14:32:01] [ENDPOINT] POST /api/users → 201 (45ms)
[2024-03-15 14:32:01] [DATABASE] INSERT INTO users (email, name) VALUES ($1, $2)
[2024-03-15 14:32:02] [AUTH] Token issued for user_id=abc123
[2024-03-15 14:32:05] [ERROR] Code node timeout after 30000ms
The format includes a timestamp, category tag, and a descriptive message. Endpoint logs also include the HTTP method, path, status code, and execution time.
Export Options
The console toolbar provides several actions for working with logs:
| Action | Description |
|---|---|
| Copy | Copy all visible logs to clipboard as plain text |
| Download | Export logs as a .txt file with timestamps |
| Clear | Clear all logs from the current view |
| Refresh | Manually fetch the latest logs from the server |
Clearing logs only removes them from your current view. It does not delete server-side log history.
Multiple Containers
If your project runs across multiple containers (e.g., in a scaled deployment), you can select which container's logs to view using the container selector in the toolbar. This is useful for debugging issues that only occur on specific instances.