Spike Arrest in Shared Flow which is configured in Pre-proxy Flow Hook

Hi,

I am trying to understand the behavior of the spike arrest policy in shared flow which is configured as pre-proxy flow hook.

Counters are created with the particular conventions which has reference to the proxy name and scope is limited to particular proxy.

But if i am using in shared flow which is attached to hook , what is the behavior ?

Is it appropriate to say that gateway itself can be restricted by this configuration?

1 2 398
2 REPLIES 2

Hello, even if the Spike Arrest is in the Shared Flow, it is still scoped to the proxy. It does not check spike arrest across proxies, it's still applied individually to each proxy

Hi @Latheef,

1. flow hooks will get included in all the proxies of on the environment, however if you have added conditions in the shared flow will execute further policies.

2. Having spikearrest in the pre flow hook is not a good idea, just think you if there is a concurrency in your application and you will reject the call without knowing if the request is coming from actual user or attacker.

3. If you need to have spikearrest for one proxy then include the shared flow for that only.