Example use case: Mixed failure scenarios

This policy incorporates both failure scenarios, and it uses both of the recovery methods set in the Origin Failure Recovery Method rule. Origin responsiveness monitoring failures trigger a failover to a backup origin; and requests that result in specific HTTP error codes trigger a different error response code that's sent to the client.

Note: This example assumes that the default configuration was used in the Origin Failure Recovery Methods—the Failure Recovery Method1 sub-rule defines a backup origin for failover, and Failure Recovery Method2 sub-rule defines a specific HTTP status code that's returned to a requesting client for failover.

Enable and configure Origin Responsiveness Monitoring

For this use case, we want to use the recovery method to failover to a backup origin for this failure scenario. Once the failure conditions set here apply, the request fails over to the backup origin defined in Failure Recovery Method1 in the Origin Failure Recovery Method rule.

Option Description
Monitor Origin Responsiveness Set this slider to "On" to enable this and access additional configuration options.
Timeouts Select the timeout threshold condition to use to trigger a retry or recovery method, or select "User-Specified" to set your own timeout. (Then, you need to input a desired time in the User Specified Timeout (seconds) that's revealed.)

The Aggressive, Moderate, and Conservative conditions use a segment-based logic and default times. They are discussed in greater detail in Timeouts section, in Origin Responsiveness Monitoring.

Enable Retry Before Recovery Set this slider to "On," if you'd like Akamai to retry after a failure before trying the recovery method.
Enable Recovery Method Set this slider to "On" to incorporate a recovery method for this failure scenario.
Recovery Method Configuration Name For this use case, we'd apply the Recovery Configuration Name set in Failure Recovery Method1, because it's set up for failover to a backup origin. (Using the examples from that process, apply the value "Alt-origin.")

Enable and configure Status Code Monitoring: Configuration 1

For this use case, we want to send a different HTTP response code to the client when the request results in one of several HTTP status codes we define. Once the failure conditions set here apply, the request fails and the response code defined in Failure Recovery Method2 in the Origin Failure Recovery Method rule is sent to the client.

While there are multiple iterations of the "Status Code Monitoring" failure scenario, we're only using Status Code Monitoring: Configuration 1" for this use case.

Option Description/Notes
Monitor Status Codes Set this slider to "On" to enable this and access additional configuration options.
Response Codes Define the origin response codes you want to trigger this specific retry or recovery method. You can input a single code entry (501) or a range (501:504). Separate multiple entries with a comma (501, 503).
Enable Retry Before Recovery Set this slider to "On," if you'd like Akamai to retry after a failure before trying the recovery method.
Recovery Method Configuration Name Input the value you applied as the Recovery Configuration Name for the applicable recovery method.

For this use case, we'd apply the Recovery Configuration Name set in Failure Recovery Method2, because it's set up to deliver a specific response code to the client. (Using the examples from that process, apply the value "Status-code-failover.")

Other Status Code Monitoring failure scenarios

There are additional "Status Code Monitoring: Configuration" failure scenarios in a policy. You could optionally configure another one to have it failover to the backup origin for specific origin status codes. To do so, you'd combine what's discussed in the previous two sections.

Apply the following settings in a the Status Code Monitoring: Configuration 2 failure scenario:

  • Monitor Status Codes. Enabled.
  • Response Codes. Input one or more different origin status codes to trigger this failure scenario. They must be different from any you've included in Status Code Monitoring: Configuration 1.
  • Enable Retry Before Recovery. This is optional. Enable this if desired.
  • Recovery Method Configuration Name. Input the Recovery Configuration Name set in Failure Recovery Method1, because it's set up for failover to a backup origin.