Monitoring Criteria (Metrics)

This metric measures the amount of bandwidth usage for the specified platform in Megabits per second (Mbps).

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.

This metric measures the percentage 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.

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.

This metric measures the percentage of requests per second that result in NONE status. This status indicates that a cache content freshness check was not performed.

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.

This metric measures the percentage 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.

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.

This metric measures the percentage 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.

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.

This metric measures the percentage 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.

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.

This metric measures the percentage 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.

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 origin shield server or an origin server.

This metric measures the percentage 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 origin shield server or an origin server.

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.

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.

This metric measures the percentage 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.

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.

This metric measures the percentage 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.

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.

This metric measures the percentage 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.

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.

This metric measures the percentage 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.

This metric measures the number of 400 status codes that occur per second. This status code indicates that the server refused to process the request due to a client error.

This metric measures the percentage of 400 status codes that occur per second. This status code indicates that the server refused to process the request due to a client error.

This metric measures the number of 401 status codes that occur per second. This status code indicates that the request lacked the credentials required for authorization.

This metric measures the percentage of 401 status codes that occur per second. This status code indicates that the request lacked the credentials required for authorization.

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.

This metric measures the percentage 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.

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.

This metric measures the percentage of 404 status codes that occur per second. This status code indicates that the requested asset could not be found.

This metric measures the number of 409 status codes that occur per second. This status code indicates that the requested action conflicts with the state of the requested content.

This metric measures the percentage of 409 status codes that occur per second. This status code indicates that the requested action conflicts with the state of the requested content.

This metric measures the number of 429 status codes that occur per second. This status code indicates that the client submitted too many requests within a short time period.

This metric measures the percentage of 429 status codes that occur per second. This status code indicates that the client submitted too many requests within a short time period.

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.

This metric measures the percentage 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.

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.

This metric measures the percentage 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.

This metric measures the total number of requests that returned a status code that was not covered by another metric.

This metric measures the percentage of requests that returned a status code that was not covered by another metric.

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.