Status Code Monitoring
Configure these failure scenarios to continually monitor for specific origin status codes that you specify, in order to apply a retry or recovery method.
Status Code Monitoring: Configuration 1
This is the primary configuration. To include it as you failure scenario:
- Set its Monitor Status Codes slider to "On"
- Set additional configuration options:
| Option | Description/Notes |
|---|---|
| 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). |
| Enable Retry Before Recovery | Set this slider to "On," if you'd like Akamai to retry after a failure before trying the recovery method. Note: A retry attempt will not reach the
origin if the initial error response is cached. The error response codes 204, 305,
404, and 405 are typically cached. You can also include additional codes to be
cached negatively via the Cache HTTP Error Responses behavior in your AMD property. |
| Recovery Method Configuration Name | Input the value you applied as the Recovery Configuration Name for
the recovery method you want to use:
Note: If you've deviated from
the default method to set up your recovery methods, verify the proper Recovery Configuration Name to use by reviewing the Origin Failure Recovery Methods rule. |
Status Code Monitoring: Configurations 2 & 3
These are additional iterations of the Configuration 1 failure scenario that you can implement to include different recovery methods for different origin status codes.
The setup and use of these failure scenarios are exactly the same as Configuration 1. However, the following apply:
- You can't use repeat origin status codes. For example, if you've added "501" as a code in Configuration 1, you can't use it in Configuration 2 or Configuration 3.