A core component of a real-time alert configuration is the metric that will be used to define when an alert notification should be sent out. A metric is a real-time statistic that provides insight into the customer experience. It reveals how much and whether content is being delivered to your customers.
Name | Platform(s) | Description |
---|---|---|
Bandwidth Mbps |
HTTP Large |
This metric measures the amount of bandwidth usage for the specified platform in Megabits per second (Mbps). |
Cache Status: CONFIG_NOCACHE per second |
HTTP Large |
This metric measures the number of requests per second that result in a CONFIG_NOCACHE status. This status indicates that a customer-specific configuration on our edge servers prevented the asset from being cached. |
Cache Status: None per second |
HTTP Large |
This metric measures the number of requests per second that result in NONE status. This status indicates that a cache content freshness check was not performed. |
Cache Status: TCP_CLIENT_REFRESH_MISS per second |
HTTP Large |
This metric measures the number of requests per second that result in a TCP_CLIENT_REFRESH_MISS status. This status is reported when an HTTP client (e.g., browser) forces an edge server to retrieve a new version of a stale asset from the origin server. |
Cache Status: TCP_EXPIRED_HIT per second |
HTTP Large |
This metric measures the number of requests per second that result in a TCP_EXPIRED_HIT status. This status is reported when a request that targeted an asset with an expired time to live (TTL), such as when the asset's max-age has expired, was served directly from the POP to the client. |
Cache Status: TCP_EXPIRED_MISS per second |
HTTP Large |
This metric measures the number of requests per second that result in a TCP_EXPIRED_MISS status. This status is reported when a newer version of an expired cached asset is served from the POP to the client. |
Cache Status: TCP_HIT per second |
HTTP Large |
This metric measures the number of requests per second that result in a TCP_HIT status. This status is reported when a request is immediately served from the POP to the client. |
Cache Status: TCP_MISS per second |
HTTP Large |
This metric measures the number of requests per second that result in a TCP_MISS status. This status indicates that a cached version of the requested asset was not found on the POP closest to the client. These types of requests are forwarded to an |
Cache Status: Total Hits per second |
HTTP Large |
This metric measures the number of successful requests per second for content on the specified platform. For the purposes of this metric, a successful request consists of cache hits and cache misses. |
Cache Status: UNCACHEABLE per second |
HTTP Large |
This metric measures the number of requests per second that result in an UNCACHEABLE status. This status is reported when an asset's Cache-Control and Expires headers indicate that it should not be cached on a POP or by the HTTP client. |
Status Code: 2XX per second |
HTTP Large |
This metric measures the number of 2xx status codes (i.e., 200, 201, 202, etc.) that occur per second. This type of status code indicates that the request was successfully delivered to the client. |
Status Code: 304 per second |
HTTP Large |
This metric measures the number of 304 status codes that occur per second. This status code indicates that the requested asset has not been modified since it was last retrieved by the HTTP client. |
Status Code: 3XX per second |
HTTP Large |
This metric measures the number of 3xx status codes (i.e., 300, 301, 302, etc.) that occur per second. This type of status code indicates that the request resulted in a redirection. |
Status Code: 403 per second |
HTTP Large |
This metric measures the number of 403 status codes that occur per second. This status code indicates that the request was deemed unauthorized. One possible cause for this status code is when an unauthorized user requests an asset protected by Token-Based Authentication. |
Status Code: 404 per second |
HTTP Large |
This metric measures the number of 404 status codes that occur per second. This status code indicates that the requested asset could not be found. |
Status Code: 4XX per second |
HTTP Large |
This metric measures the number of 4xx status codes (i.e., 400, 401, 402, 405, etc.) that occur per second. This status code indicates that the requested asset was not delivered to the client. |
Status Code: 5XX per second |
HTTP Large |
This metric measures the number of 5xx status codes (i.e., 500, 501, 502, etc.) that occur per second. This status code indicates that the server was unable to honor the request. |
Status Code: Other per second |
HTTP Large |
This metric measures the total occurrences for all status codes that are not covered by another metric. |
Status Code: Total Hits per second |
HTTP Large |
This metric measures the number of requests per second. You can use this option as a baseline indicator to see the percentage of total hits that a particular status code comprises. |
Total Connections |
HTTP Large |
This metric measures the average number of new active connections per second. |