Process Log

The process log surfaces runtime stdout/stderr from Coderunner workloads and related services. Control Plane proxies LogQL queries to Loki — it does not store log lines in Postgres.

Customer Portal

From Process Log:

1. Select a workspace
2. Optionally filter by app, runner, or search string
3. Toggle Live for 5-second polling or pause to inspect a snapshot

If Loki is unavailable in an environment, the UI shows an empty state until the observability stack is connected.

API

GET /v1/workspaces/{workspace_id}/process-log?workspace_id=...&app_slug=...&q=...
Authorization: Bearer <token>

Requires read on the workspace. Response is a JSON array of log lines with timestamps and labels.

Data path

Coderunner pod → Fluent Bit → Loki
                                    ↑
Control Plane LogQL proxy ← Customer Portal / API

Log retention and indexing are configured in the platform observability stack — not per-tenant in Control Plane metadata.

Link from Coderunner

The Coderunners page links directly to Process Log with workspace and app filters pre-filled when viewing a runner.

Related

• Process log guide — UI walkthrough
• Audit log — security audit trail (different store)
• Coderunner integration — workload runtime