Edge function accounting: numbers do not add up

I have recently migrated my Nuxt project from using functions to edge-functions. The result has been a 100x increase in the number of requests according to the billing dashboard (from hundreds of requests per day to tens of thousands).
My app usage behaviour has not changed: still the same number of users per day (order of tens, between 20-50). Uploaded manifest.json file still has the right excludePath for static assets.
My hypothesis is that there is something wrong accounting for edge function invocations, although it is not easy to validate this.

Has anyone else experienced a similar issue? What would be the right way to validate the hypothesis?

We’ve routed this request to our helpdesk, we’ll follow up via email.

Thank you, looking forward to hearing you by email.
Meanwhile, I have instrumented my nuxt app to log every request through middleware. Now I can easily curl a specific URL in my site and check edge function accounting (through the billing dashboard, looking at netlify API responses for /access-control/analytics-api/v2/accounts/XXX/usage_insights/edge_functions.

The results show that, depending on the specific URL curl’ed, Netlify accounts 6-15 invocations, instead of one.

I believe I have found the source for the misterious traffic. In my nuxt project I was storing some static files under public/img that were being requested by an abussive crawler and served by the edge function. Unfortunately, it was impossible to debug but for trial and error due to nitro middleware not triggering for static assets (or adding an additional edge function to log every request, which is what I ended up doing).

As a feature request: functions have the option of setting preferStatic to offload certain traffic from the function. This is unfortunately not possible with edge functions and it would be great to have.