OrbitsDocs
esc
    Open Orbits
    ObserveRuntime logs

    Runtime logs

    Every request your app was sent and every line it printed while running, kept for 7 days. Search and filter them on the project's Logs page, from the CLI or through the API.

    What the Logs page shows

    Open a project and choose Logs. The page lists two kinds of entry, newest first:

    • Requests: every request Orbits' edge sent to one of the project's deployments, production and previews alike. Each has its status, method, path and how long it took.
    • Functions: every line the project's deployments printed while running, on standard output or standard error. Each has its message and the stream it came from.

    Build output is not here. It belongs to a deployment, so it is on that deployment's page (see build logs and runtime logs below).

    Requests and output lines are separate entries, and Orbits does not link them: an app's output is whatever it printed, whichever request it happened to be serving. To tie the two together, log the X-Request-Id header. The edge sends it with every request, and the same id is shown as the request's Request ID on the Logs page.

    Live and Paused

    The page starts Live: it checks for new entries every few seconds and adds them at the top. Choose Paused in the top corner to stop it moving while you read; choose Live again to carry on.

    Search and filters

    The toolbar above the list narrows what you see. Filters combine, and the URL keeps them, so you can share a filtered view with a teammate.

    ControlWhat it does
    Search logsMatches a path or a message, in any case, or exactly a request ID, a status (502) or a method (POST). A request ID on its own (32 hex characters, as the edge makes them) finds just that request. Up to 200 characters.
    SourceRequests or Functions. All shows both.
    LevelInfo, Warning or Error.
    Status2xx, 3xx, 4xx or 5xx. Requests only: output lines never match a status.
    TimeLast hour (the default), Last 24 hours or Last 7 days.

    How levels are decided

    EntryInfoWarningError
    A request1xx, 2xx and 3xx answers4xx answers5xx answers
    An output lineAnything elseThe line mentions a warningThe line was written to standard error, or mentions an error

    When nothing matches, the page says so and offers to widen the time range or clear the filters. The count above the list goes up to 10,000; beyond that it shows 10,000+. Choose Load more at the foot of the list for older entries.

    One log entry

    Pick an entry and the panel beside the list shows all of it.

    For a request: the status and METHOD /path, the time, the duration, the region, the host it was sent to, the deployment that answered (linked to its page) and the request ID, then Request headers.

    For an output line: its level, the whole Message, the time, the stream (stdout or stderr), the region, the host and the deployment.

    A link to an entry keeps working while the entry exists. Once it is older than 7 days, it is gone.

    What is and isn't stored

    Logs are built to be safe to keep:

    • Query strings are never stored. A path is kept without its ?…, because query strings often carry tokens.
    • Client IP addresses are masked, to the first two parts of an IPv4 address (102.89.x.x) or the first three groups of an IPv6 address.
    • Only four request headers are kept: user-agent, accept, content-type and referer, plus x-forwarded-for, masked. Cookies and authorization are never read.
    • An output line is kept without its colour codes, up to 8,192 characters.

    What your app prints is kept as it was printed, so don't print secrets.

    Build logs and runtime logs

    Build logRuntime logs
    What it isWhat the build printed, step by step: Queued, Cloning repository, Installing packages, Building, Uploading, Going liveRequests to the running app, and what it printed while running
    WhereThe deployment's page, and live on the page while it buildsThe project's Logs page
    SizeAt most 5,000 lines per buildEverything, for 7 days
    Follow it liveYes, while the build runsYes, with Live

    A failed build is told in its build log, not here. See deployments.

    From the CLI

    Terminal
    $ orbits logs --runtime$ orbits logs --runtime -f --level error$ orbits logs --runtime --since 24h --source requests --search /checkout

    -f follows new entries as they arrive. --since takes 1h, 24h or 7d. orbits logs <deployment> (without --runtime) shows a build's log instead. See the CLI.

    From the API

    GET /v1/teams/{team}/projects/{project}/logs returns a page of entries with the same filters as the page: q, source (requests or functions), level (info, warning, error), status (2xx to 5xx), range (1h, 24h, 7d; default 1h) and limit (1 to 500, default 50). Send the answer's next_cursor back as cursor for the next page.

    Terminal
    $ curl -s "https://api.theorbits.app/v1/teams/acme/projects/storefront/logs?level=error&range=24h" \    -H "Authorization: Bearer $ORBITS_TOKEN"
    One entry
    {
      "id": "log_…",
      "at": "2026-11-10T09:14:03.218Z",
      "source": "requests",
      "level": "error",
      "status": 502,
      "method": "POST",
      "path": "/api/checkout",
      "duration_ms": 1840,
      "message": null,
      "stream": null,
      "request_id": "4f1c…",
      "host": "storefront.theorbits.app",
      "region": "abj-1",
      "deployment": { "id": "dpl_…" },
      "headers": [["user-agent", "Mozilla/5.0 …"]]
    }

    GET .../logs/{log} returns one entry by its log_ id. Both answer 503 if logs can't be read for a moment: try again shortly. Any member of the team can read logs, including viewers and a read-only API token. The full reference is at API › Logs.

    Was this page helpful?

    Updated