Analytics improvement: Updated logic for HTTP response code classes
We are excited to announce our plans to supplement our Analytics product with the capability to track additional HTTP status codes via our MCC portal and REST API service. In preparation for this enhancement, the manner in which the Real-Time Statistics module, including Real-Time Alerts, and our Edge Performance Analytics module report 2xx, 3xx, 4xx, and 5xx HTTP status codes, will conform to industry standards.
These classes of HTTP status codes exclude data that may be tracked individually. For example, the 4xx class currently excludes 403 and 404 status codes, since reporting data and alerts may be generated separately for each.
Starting on January 31, 2018, the 2xx, 3xx, 4xx and 5xx classes of status code will no longer exclude data based on whether a status code may be tracked individually. For example, the 4xx class of status code will now track status codes from 400 to 499.
This change is for the Edgecast Content Delivery Network environment. TRANSACT will not be affected.
The following reports and APIs are impacted:
- Real-Time Statistics: HTTP Large, HTTP Small and ADN
- Real-Time Alerts
- Edge Performance Analytics: 4xx Errors
- Edge Performance Analytics: 5xx Errors
- Real-Time Statistics: Get Current Status Code Statistics
- Get Current Edge CNAME Statistics
- Get Current Edge CNAME Statistics II