While buffering can help flatten out the load from Web events generated in bursts, not all providers support buffering, and those that do have finite limits on the size of their buffers. To help control noise and mitigate potential attacks against the health monitoring system, you can turn on throttling and coalesce or discard events that are occurring too often. Throttling is controlled via the three optional attributes on a rule shown in Table 7-4.
To make it easy to reuse a set of throttling parameters on many different rules, you can factor these three attributes into a health monitoring profile[5] and then refer to that profile from your rules. The root web.config already defines two profiles (shown in Listing 7-8) or you can define your own.
Listing 7-8. Using health monitoring profiles
While you might not turn on throttling to begin with, it's good to know that it's there and that an administrator can turn it on in case of an attack or to eliminate excess noise. |