Vercel

This guide configures traces, and logs once log drains are available. Replace YOUR_INGEST_KEY with your key on your server, never in a public example.

1. Create a signed Logs drain (not available yet)

Once log drains are available, add a Logs drain in Vercel Team Settings, Drains, and select projects/environments. Copy its signature verification secret into Usage and settings, Collection, Vercel signing secret. Site Qwality requires x-vercel-signature using HMAC-SHA1 over the exact request bytes, even though Vercel calls signing optional. Save the secret before testing the drain.

Destination: https://otlp.siteqwality.com/v1/vercel
Encoding: JSON or NDJSON
Authorization: Bearer YOUR_INGEST_KEY
X-Service: my-service
X-Env: production

2. Create a separate OTLP Traces drain

Choose Traces as the drain data type. The log-drain signing requirement applies to /v1/vercel; traces use the normal OTLP authorization contract. Drain availability depends on your Vercel plan.

Destination: https://otlp.siteqwality.com/v1/traces
Encoding: OTLP HTTP Protobuf or JSON
Authorization: Bearer YOUR_INGEST_KEY

3. Generate and verify

Do not send Speed Insights, Web Analytics or Audit Log envelopes to the log adapter. Never put the ingest key in NEXT_PUBLIC_* variables.

Redeploy the project, make a request, and emit a server log. Check the Vercel drain test result and the Site Qwality explorer.

See your data

Open Logs, Traces or Metrics. New data usually shows up within a minute, and a page that says it is waiting for data switches to your data on its own. Nothing arriving? See what each status code means in failure handling.

Production checklist

Store the key in your platform secret mechanism, rotate it when exposed and remove test keys. Set a stable service.name and deployment.environment.name; avoid user IDs or unbounded values in metric labels. Prefer a persistent queue, bounded retries and exporter failure monitoring. Review redaction and processors before increasing traffic.