#Unable to set up Vercel Drain -> Sentry

13 messages · Page 1 of 1 (latest)

ruby token
#

I am expecting a 'x-vercel-verify' header in response to this curl:

curl -I -X POST https://REDACTED.ingest.us.sentry.io/api/REDACTED/integration/vercel/logs/
-H "x-sentry-auth: sentry sentry_key=REDACTED" -H "Content-Type: application/json"

instead I get a 202 with no x-vercel-verify header. full response:

HTTP/2 202
server: nginx
date: Thu, 13 Nov 2025 00:25:36 GMT
content-length: 0
vary: origin, access-control-request-method, access-control-request-headers
access-control-allow-origin: *
access-control-expose-headers: x-sentry-error,x-sentry-rate-limits,retry-after
cross-origin-resource-policy: cross-origin
strict-transport-security: max-age=31536000; includeSubDomains; preload
via: 1.1 google
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

more specifically, this is causing the terraform resource of type vercel_log_drain to fail to create. Full terraform error here:

│ Error: Error creating Log Drain
│
│ with vercel_log_drain.dashboards_to_sentry,
│ on log-drain.tf line 14, in resource "vercel_log_drain" "dashboards_to_sentry":
│ 14: resource "vercel_log_drain" "dashboards_to_sentry" {
│
│ Could not create Log Drain, unexpected error: validation_error - Cannot validate endpoint url: either the url is not reachable or the
│ x-vercel-verify header in the response did not contain the expected value

Terraform Registry
ruby token
#

As per #1346614324260765726 I have enabled the early adopters toggle on my account and now the above curl is returning a 403.

tough sequoia
#

Hey @ruby token - are you able to share your org slug and sentry project you used? Feel free to reach out to [email protected]

That’ll help us start to investigate this

#

Also, x-vercel-verify shouldn’t be required by log drains anymore. I would reach out to Vercel support as this is definitely a issue on the Vercel side

#

Ahhh

ruby token
#

100%

#

I just imported my log drain created in my vercel GUI into my state file and now I can manage it.

tough sequoia
#

Ah sweet. Would you be open to sharing that terraform config? I can add it to the docs

ruby token
#

once done, yep

#

resource "vercel_log_drain" "_" {
team_id = "team_REDACTED"

delivery_format = "json"
endpoint = local.sentry_endpoint

headers = {

"x-sentry-auth" = "sentry sentry_key=REDACTED"
"Content-Type"  = "application/json"

}

environments = ["preview"]
sources = ["lambda"]

project_ids = local.dashboard_project_ids

sampling_rate = 1

}

#

however, importing is nearly useless because if there is a change required, TF will destroy and the nbe unable to re-created the drain... of course.

#

also your endpoint is actually sending a 403 intermittently when I try to set up a new drain. Have to repeatedly try until is goes through.