Recently I experienced a 20-30x spike in http responses as shown in the image.
Unfortunately my own tracking did not catch this, so I’m wondering if there is a way to get more information about the requests that came through?
Just being able to read the logs with the path that the request came in at would be helpful.
It looks like Fly.io’s metrics generally don’t include information about the URI path:
I suspect the same “tricky to do so” applies to logs as well, but I don’t know that for certain, 
.
It really would be handy, though.
Aside: Fly.io’s built-in retrospective logs have been getting flakier and flakier; for example, the following snippet from the most recent Infrastructure Log…
The Volumes we used for this cluster were undersized for the amount of metadata growth we experienced, and queries to the cluster began generating 500 errors.
They’ve been saying recently that any feature improvements would only occur in a (still hypothetical) future extra-cost version.
Yea I mean, I think that’s pretty fair. I should have added my logs/metrics on all every incoming http requests instead of limiting it to the intended /api routes.
I wouldn’t be surprised if it was a bunch of wordpress /wp/ crawl although 1k in 1 min seems too high for that.
