Skip to Content
ConnectorsVercel logs

Vercel logs — vercel

Push source for Vercel logs: point a Vercel log drain (JSON) at the source’s ingest endpoint. One event per log entry, keyed by project, with environment and source as labels. A single drain can carry multiple projects; they appear as distinct entities.

Prerequisites: the ingest endpoint must be publicly reachable — Vercel delivers from its cloud. Use a deployed instance or a tunnel; a bare localhost daemon will not receive drains.

Set up

Ask a connected agent:

Use navflow to create a vercel source and give me the ingest URL for the log drain.

The agent calls create_source (no required config) and returns the source’s ingest endpoint — then add the drain in Vercel as below. Walkthrough: Ingest Vercel logs.

Then, in Vercel: Team Settings → Log Drains → Add Log Drain — endpoint = the ingest URL, delivery format = JSON. Vercel verifies the endpoint via an x-vercel-verify header; NavFlow echoes the value Vercel sends, or set NAVFLOW_VERCEL_VERIFY=<value> on the daemon if Vercel expects a pre-shared one. If NAVFLOW_INGEST_TOKEN is set, add it to the drain as a custom header (X-NavFlow-Token: <token>).

Configuration

No connector-specific fields — just labels.

Provided labels

project (the key; from the payload’s projectName, else projectId), environment (production | preview), source (lambda | build | edge | static | external | redirect), path, host, deployment, branch.

Verify

Once the drain is saved and traffic flows: Recent events shows entries arriving; Fields shows which projects appear and each field’s coverage. If project reads sparse, pick a denser field as the key, or slice by source / environment.

Last updated on