Logical Timeout/Slow Response Policy?

[znelson32]

Summary: What are you wanting to achieve?
Isolating slow responses / logical timeouts on a service call which contribute to the opening of a circuit breaker, however, accomplishing this by allowing the service calls to complete. For ex., if a service call exceeds a Timespan, allow it to continue (because it may ultimately be successful) but logically fail the call in regards to the circuit breaker's perspective such that if enough calls are slow the breaker will open. The use case could be slow database queries where after n-seconds you want to stop additional calls from piling up on the database server but you want the initial few calls to complete (or ultimately fail outright but that part is already something Polly does).

What code or approach do you have so far?
Nothing. Unsure of how to implement this in a custom AsyncPolicy as it appears the mechanism to open a breaker (or vote for its opening) is either throwing exceptions (which would terminate the service call) or fully opening the breaker via Isolate() which any given thread should not be able to do on its own.

It is always useful to see:

• code of any policy declarations,
• code of the calls to .Execute/AndCapture/Async(...)

[martincostello]

@martintmk Is there anything in v8 that would fulfil this feature request?

[github-actions]

This issue is stale because it has been open for 60 days with no activity. It will be automatically closed in 14 days if no further updates are made.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.