Getting occasional 404s for _axiom/web-vitals call on PROD

[jerang]

Noticed my production dashboard is showing a small percentage of 404 errors for the web vitals call. Any idea what's causing this and how I can patch it? I do see the web vitals working since there are a number of successful calls for most users.

Secondly, is there a way to get this call to work locally?

[bahlo]

Hey @jerang, thanks for the issue -- it's something we're aware of and looking into 👍

Secondly, is there a way to get this call to work locally?

You can copy the NEXT_PUBLIC_AXIOM_INGEST_ENDPOINT from your environment and expose it locally.

[agustinl]

Hi @bahlo, to prevent create a duplicated issue, I'm seeing some requests to non-existents paths like /wordpress /wp /old /new /2020 etc.

This is something related to this issue?

Thanks!

[dasfmi]

Hi @bahlo, to prevent create a duplicated issue, I'm seeing some requests to non-existents paths like /wordpress /wp /old /new /2020 etc.

This is something related to this issue?

Thanks!

those are probably bots or web crawlers maybe trying to access those routes that don't exist on your app, I believe its not related to next-axiom.

[bahlo]

@jerang do you still see this happening?

[jerang]

I am still seeing it; pulled data using query:

vercel
| where ['vercel.route'] contains "axiom" and ['request.statusCode'] != 200
| summarize count() by bin_auto(_time), ['request.host'], ['request.path']

Post requests look correct to "https://vercel-vitals.axiom.co/api/v1/send"