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

Agent

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. It then add the drain in Vercel as below. Walkthrough: Ingest Vercel logs.

Console

Sources → Add source → vercel. There is no required config; the project (key), environment, and source labels are pre-filled. Save.

The source page shows its ingest endpoint. It is a stable URL of the form https://<host>/ingest/<ingest_key>. Copy it.

YAML / API


- name: web-logs
  connector: vercel
  config:
    labels:
      - { name: project, field: project, primary: true }
      - { name: environment, field: environment }
      - { name: source, field: source }

Or POST /api/sources with the same object; the response includes the ingest_key.

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, which NavFlow echoes back from Vercel’s verification request. On a secured instance (navflow up --auth), add an ingest-scoped API key to the drain as a custom header (Authorization: Bearer <key>).

Configuration

No connector-specific fields — just labels.

Provided labels

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.

Vercel logs — vercel