Your Vercel project.
Logs in Scribed.

Forward runtime logs

A log drain forwards new log events from Vercel to Scribed. After saving your project connection, choose Enable logs when available so Scribed can configure the drain for you. Connections with manual setup show Drain setup instead. Availability depends on your connection and the setup options currently enabled for it.

1. Check the selected project. The default is production runtime logs from functions and edge functions. Open the advanced options before enabling if you need preview logs or additional sources.
2. Review the selection and choose Enable logs. Scribed creates the drain and tests delivery. If permission is required, choose Review Vercel permissions and accept the requested Drains permission in the installation’s settings. Return to Scribed and choose Check status.
3. Check the drain status and last delivery test. Make a normal request to your project in a selected environment, then check the last log received and View logs → Recent logs. A delivery test does not count as a real log event.

Once configured, the selected environments and sources stay fixed in this setup. Retry checks the same drain. If you already created a manual drain for this endpoint, keep using it or review and remove it in Vercel before enabling automatic setup.

Manual setup

If automatic setup is unavailable, use the manual fields in Drain setup. Keep the endpoint and signing secret private; the connection owner can reopen them later.

1. In Vercel, open your team’s Settings → Drains → Add Drain. Choose Logs and select only the project connected in Scribed. Choose the log sources and environments you want to forward.
2. Select Custom Endpoint. Copy Scribed’s Endpoint URL into the matching Vercel field and choose JSON for Format.
3. Copy Scribed’s Signature Verification Secret into that field in Vercel. Add Custom Headers only if Scribed supplies them; otherwise leave that field empty.
4. Save the drain and check its delivery status in Vercel. Make a normal request to your project, then open View logs → Recent logs in Scribed and refresh to confirm that a new event arrived.

Review what your application writes to logs before forwarding them. Avoid passwords, access tokens and unnecessary personal information. Drain availability, delivery and charges depend on your Vercel plan; Scribed usage follows your account’s billing.

See Vercel’s drain setup instructions and drain signing requirements for the current provider settings.

Read logs and findings

Choose View logs on the Vercel connection. Recent logs show received log events; Findings summarize reported runtime issues and available deployment status checks. Check the project and access context before reading or sharing a result.

The view reports the last 24 hours and indicates when results are limited. Deployment checks and runtime log delivery have separate status: an active OAuth connection does not prove that a drain is delivering, and an empty window does not prove that the project has no problems. Use Vercel to investigate the original deployment.

Choose workspace access

Workspace access is off by default. The connection owner can allow access in a workspace where they are an owner or administrator.

1. Open Workspace access on your Vercel connection.
2. Choose a workspace, confirm the selected project, and allow Recent logs, Findings, or both.
3. Teammates with the required workspace access can open View logs → Workspace access and select the shared connection. Their own workspace permissions still apply.
4. To stop sharing, return to the connection’s Workspace access, review the workspace and revoke its access.

A grant covers this project and the kinds of results you chose. It does not give the workspace your Vercel credentials, access to another project, permission to change deployments, or consent for unattended Runs. Revoking a grant stops future workspace reads.

Reconnect or disconnect

Use Update connection or Reconnect when authorization expires or you want to select a different project. Review Vercel authorization and save the project again. Replacing the connection invalidates earlier workspace grants; allow each workspace again only after checking the new connection. Review the current log setup before enabling logs for the new connection.

To remove the connection, choose Disconnect in Scribed and confirm. This immediately stops Scribed access and sharing, and requests removal of saved Vercel credentials and stored runtime log history. When Scribed created the drain through Enable logs, it also removes that specific drain. If cleanup cannot finish, Scribed keeps it pending for retry. Remove manually created drains yourself in Vercel so they stop sending events.

Disconnecting in Scribed does not uninstall the Vercel integration. To revoke its provider authorization, remove Scribed from the relevant account or team’s integrations in Vercel. Review Vercel’s removal confirmation carefully: uninstalling an integration can also remove resources associated with that installation.

Troubleshooting