The lowest edge bandwidth for given objects and filters. The peak edge bandwidth for given objects and filters. The edge bandwidth for given objects and filters. The lowest volume that was served from cache as a percentage of total volume served.Įdge bits per second. The peak volume that was served from cache as a percentage of total volume served. The average volume that was served from cache as a percentage of total volume served. The volume of traffic served by Akamai that did not require hits on your origin.Īverage bytes offload. A request method indicating the action performed on a resource.īytes offload. PUT/POST Requests - Request traffic from PUT and POST operations.GET/HEAD Responses - Response header traffic from GET operations.PUT/POST Responses - Response traffic from PUT and POST operations.All Responses - Includes all response traffic.HTTP traffic to be included in the report data. An HTTP response status code, for example, 404. A class of HTTP response status codes, from 0XX through 6XX. An indicator showing success or failed HTTP response. If no IP version is selected, the report shows data for both IPv4 and IPv6. Supported array values are IPv4 and IPv6. Distinguishes secure traffic from non-secure traffic. Selecting a non-cacheable filter lets you see non-cacheable traffic even if offload is zero, offload for content that is redirected responses served from the edge, and offload for content generated at the edge.ĭelivery type (optional). Distinguishes cacheable content from non cacheable content. The metrics show average traffic data (not peak).Ĭacheability. There is no offload for non cacheable content. Some filters and metrics depend on your selection.ĭepending on whether the cacheability filter is enabled or not, the offload graph is yellow (for cacheable) or purple (for non cacheable) data. You can choose to show the base metrics for the page in hits or bytes. This means edge traffic (traffic from the edge servers to end users), midgress traffic (traffic between the servers), and origin traffic (traffic from your origin). The Traffic report provides hits, volume, bandwidth, and offload data over time for your web delivery products. Traffic in portions of Southeast Asia may not accurately reflect PNI usage, even though those connections are utilized. Estimated PNI bytes / cloud origin bytes for this CP code and time frame. Estimated bytes of traffic egressing through PNIs for this CP code over this time frame. Estimated bytes of traffic from cloud origin for this CP code over this time frame. Interconnect traffic by CP code (table) metrics Estimated bytes of traffic egressing through PNIs for date range. Estimated bytes of traffic from cloud origins for date range. Estimated PNI egress traffic as opposed to cloud origin egress traffic. Estimated cloud origin bytes served through PNIs for time period. Estimated bytes served from cloud origins for time period. Groups let you narrow down your content to groups of CP codes. All CP codes have ties to one or more services, which are tracked and reported under that CP code. Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. For optional filters, making no selection returns all associated data for that filter.ĬP code (required). Select at least one required filter in every report. Your cloud service usage report may show dates in local time, so take this into account if comparing Akamai reported origin traffic against your cloud provider’s reporting. The KPI sections shows estimated Total Traffic, Traffic over PNIs, and percentage of Traffic using PNIs. The Cloud Interconnects behavior maximizes traffic flow through PNIs provided by some cloud hosting providers. The Cloud Interconnects report allows you to estimate how much of your cloud origin egress traffic is successfully sent through Private Network Interconnects (PNIs).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |