In the previous articles in this series, we have seen how to author custom reactive and proactive Polly policies:
- Part I: Introducing custom Polly policies and the Polly.Contrib
- Part II: Authoring a proactive custom policy (a policy which acts on all executions)
- Part III: Authoring a reactive custom policy
In this article we'll build our first reactive custom Polly policy: a policy to log exceptions or fault-results.
Polly polices fall into two categories: reactive (which react to configured faults) and non-reactive / proactive (which act on all executions). To author a proactive policy, see Part II: Authoring a proactive custom
In this article we'll build our first custom Polly policy: a proactive Policy to capture execution timings.
Polly polices fall into two categories: reactive (which react to faults) and non-reactive or proactive (which act on all executions). To author a policy which reacts to faults, see Part III: Authoring a
Introducing custom policies
The Polly team have long wanted to allow users to extend Polly's capability with custom policies.
Polly v7.0 introduces a simple mechanism for authoring custom policies which integrate fully with the existing Polly architecture: the fault-handling syntax, the execution overloads, and the ability to combine policies