*Use case: *customer has implemented hundreds of methods and want per second edge limit to be differentiated per method.

Solution:
Limiting by path scoped by service is already possible using the Edge limiting policy. The policy accepts any time window, so it's possible to limit per second.

In order to limit by path, the user just needs to specify it using liquid (see 5.1.6.3. Liquid templating)
And there's an attribute to select per-service/global (see 5.1.6.2. Limit definition)

Proposing to add this example to the current documentation https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.4/html/deployment_options/apicast_policies#edge_limiting

For reference https://github.com/3scale/APIcast/pull/991

And here's an example documented by David https://github.com/3scale/APIcast/pull/1040