Specifying a custom EndpointCounterKeyBuilder per route

[Phil-G]

I have a route that needs special handling. Something like GET /User/{userId}/Info
I want the route to have a limit, regardless of the IP or client ID. GET /User/1/Info should be tracked separately from GET /User/2/Info

It would be helpful to have more config granularity per route to prevent endpoints from getting overloaded and taxing the DB.

[kamilzzz]

Maybe you could apply custom attribute to endpoints, implement custom ICounterKeyBuilder where via injected IHttpContextAccessor you could read endpoint metadata, and then act accordingly?

Then you could have some special handling for annotated endpoint and use default EndpointCounterKeyBuilder for the rest of them? At least in theory as I didn't even try that :D