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.