![]() 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. MOA will provide no technical support.The Cloud Interconnects report allows you to estimate how much of your cloud origin egress traffic is successfully sent through Private Network Interconnects (PNIs). It is the sole responsibility of the user to keep all files current with those on the web site. The MOA assumes no responsibility for any loss due to any computer or software generated problems associated with these files. This report is not to be sold, or used in any process for resale as a value-added product, or otherwise distributed for profit in any form without expressed written consent of the Traffic Department. Note: The information that is provided on this web site is a property of the MOA. Use of another older version may result in instability or inoperability.Ī CD or hard copy may be obtained from the Traffic Department at 343-8406. The content is based on information available at the time of its creation therefore, any action such as additions or corrections to any subsequently received data is not included in this report.Īdobe Acrobat Reader version 6.0 or higher is needed to view these files. It is intended for informational purposes only. The publication offers important information about: the department, roadway and trail volumes, speed studies, accident statistics, roadway information, locations of traffic features, and safety analyses ranking. The annual report is prepared by the Municipal Traffic Department.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |