Report modules are listed on the Analytics menu. After selecting the desired module, click the desired report from the side navigation bar.
Learn more about report navigation.
If a reporting module is hidden or disabled, then that reporting module has not been purchased. Please contact your CDN account manager for additional details.
Key information for navigating through the available reports:
- Solid Arrow (
): A solid arrow indicates that there are additional types of reports available. Typically, clicking a solid arrow will result in additional sub-reports appearing directly below it. The expanding and collapsing nature of this report section is indicated by a solid down arrow (
). If selecting a solid arrow doesn't expand/collapse a section, then an additional report can be viewed from within the report that is displayed for that item. - Hollow Circle (
): A hollow arrow indicates that a report will be displayed when you select that item.
Most reports are automatically generated upon loading the corresponding page. After which, modify the report's settings to improve its relevancy.
To generate a report
-
Navigate to the desired reporting moduleCore Reports, Advanced Content Analytics, Real-Time Statistics, or Edge Performance Analytics and then click on the desired report.
Most reports require or allow the selection of a delivery platform. Platform selection is typically performed when navigating to the report.
-
Perform one or more of the following steps:
The available settings vary by report. For example, there are no filtering options for Real-Time Statistics reports. Real-Time Statistics always display current information on CDN activity for your account.
Filtering by POP (Core Reports Module)
The majority of the reports in the Core Reports module allow data to be filtered by the POP through which the request was served.
Set the Edge Nodes option to either of the following:
- All Edge Nodes: The report will contain data for all POPs.
- POP: Select a POP from the list to filter the report to only show data for the requests served through the selected POP.
Modifying the Edge Nodes option will automatically refresh the report.
Filtering by Time
The time period for which data will be reported may defined for most reports. The available filtering options for defining this time period are described below.
| Time Period | Description |
|---|---|
|
Month Year |
Configures the report to display data for the selected month/year combination (e.g., July 2017). This period starts at midnight on the first day of the month and ends at 23:59 on the last day of the month. |
|
Past 24 Hours |
Configures the report to display data for the last 24 hours. Upon selecting this option, the report's start/end date will be updated to a 24 hour period that ends at the top of the hour of the current hour. Example: If it is currently 10:30 a.m., then the 24 hour period would start at 10 a.m. on the previous day and end at 10 a.m. on the current day. |
|
Today |
Configures the report to display data for the current day. Upon selecting this option, the report's start date/time will be updated to read 00:00 (i.e., midnight) of the current day. The report's end date/time will be the current date and time. |
|
This Week |
Configures the report to display data for the current week. Upon selecting this option, the report's start date/time will be updated to read 00:00 (i.e., midnight) for a date 7 days prior to today. The report's end date/time will be the current date and time. |
|
This Month |
Configures the report to display data for the current month. Upon selecting this option, the report's start date/time will be updated to read 00:00 (i.e., midnight) for the first day of the current month. The report's end date/time will be the current date and time. |
|
Yesterday |
Configures the report to display data for yesterday. Upon selecting this option, the report's start date/time will be updated to read 00:00 (i.e., midnight) of the previous day. The report's end date/time will be 23:59 of the previous day. |
|
Last Week |
Configures the report to display data for the last week. Upon selecting this option, the report's start date/time will be updated to read 00:00 (i.e., midnight) for a date that is 14 days prior to the current date. The report's end date/time will be 23:59 for a date 7 days prior to the current date. |
|
Last Month |
Configures the report to display data for the previous month. Upon selecting this option, the report's start date/time will be updated to read 00:00 (i.e., midnight) for the 1st of the previous month (e.g., 2017-07-01 00:00). The report's end date/time will be 23:59 for the last day in that month (e.g., 2017-07-31 23:59). |
|
Custom |
Allows a custom start/end date/time to be applied to the report. Define this time period through the From and the To option, respectively.
Custom time periods should be limited to approximately 1 month. Specifying a longer time frame may cause a long delay or even prevent the report from being generated. |
The set of available time filtering options varies by report type.
The report will be updated upon selecting a predefined time period from the Date Range option. Apply a custom time period to a report by clicking Go.
Relationship between Start/End Time and Data Reported
A factor that affects the set of data that will be included in a report is the inclusive nature of start and end date/times. In order to understand what this means, you will need to know that data is reported in chunks of time (e.g., 5 minutes, 1 hour, 1 day, etc.). A report will include all of the chunks that fall within the specified time period and the chunks that correspond to the specified start and end date/time. This will occur regardless of whether the specified start and end date/time falls at the start, middle, or end of a chunk of time.
A few key facts about how time chunks affect or interact with report data:
- The amount of time covered by a chunk varies for each type of report. This time interval can either be 5 minutes, 1 hour, 1 day, or 1 month.
- A report's time chunk should not be confused with the date/time range used to generate the report. Please refer to the documentation provided for the desired report to find out the time chunk that it uses to report data.
- If a start/end time cannot be specified for a report, then the report will include data for the specified start/end date. For example, specifying a date range of "2017-08-14 to 2017-08-15" will include data for both 8/14/2017 and 8/15/2017.
- The start and end time specified for Edge Performance Analytics reports is irrelevant. It will always include all data that took place on the specified start and end date (as demonstrated in the above note).
- A start or end date/time cannot be specified for monthly reports (e.g., Traffic Summary). A date range is not displayed for this type of report, since report data will always be limited to the specified month (e.g., 08-01-2017 00:00:00 – 08-31-2017 23:59:59 GMT). As a result, this case is not covered in this section.
It is important to know the following information when generating or viewing a report:
- What is the report's start and end date/time?
- What type of time chunk is used to report data?
The above information can be used to identify the exact time period that will be covered by a report. Simply make sure to account for the chunk of time used by the report to figure out the exact time period for which CDN activity will be reported.
The following table illustrates how the exact time period that will be included in a report can be calculated for each type of time chunk. This example assumes that the following date/time range was used to generate the report:
- Start Date/Time: 2017-08-01 07:02:00
- End Date/Time: 2017-08-02 00:00:00
| Time Chunk | Actual Start Date/Time | Actual End Date/Time |
|---|---|---|
|
5 Minutes |
2017-08-01 07:00:00 |
2017-08-02 00:04:59 |
|
1 Hour |
2017-08-01 07:00:00 |
2017-08-02 00:59:59 |
|
1 Day |
2017-08-01 00:00:00 |
2017-08-02 23:59:59 |
Reports & CDN Activity
Several reports (e.g., Traffic Summary, Bandwidth, and Data Transferred) provide information on the CDN response to the client. The data used to calculate these reports includes:
- The CDN response that is sent from a POP to a client.
-
- Origin Shield: The traffic that is sent from the Origin Shield server to the POP serving the request.
HTTP Streaming
Traffic statistics for the following HTTP streaming solutions are included in reports generated for the HTTP Large platform:
- HTTP Progressive Download
- Dynamic Cloud Packaging
- Smooth Streaming
Traffic statistics for a specific combination of a streaming solution and origin may be tracked via custom reports. A prerequisite for custom reports is to stream content over an edge CNAME. This edge CNAME must be configured to point to the desired streaming solution and custom reports must be enabled on it.
Unit Conversion
Although CDN activity data is stored in bytes, the value displayed in a report is a much larger unit (e.g., Gigabytes or Terabytes). This makes it easier for users to assess and analyze CDN traffic based on report data. In order to display data as a larger unit, it must undergo a conversion process from Bytes to Kilobytes to Megabytes to Gigabytes to Terabytes. The conversion factor used in this calculation is 1000 instead of 1024. This has the benefit of simplifying the reporting interface and eliminating confusion for general users in differences between decimal and binary representation of these values.
The above conversion process complies with the convention set by IEC in accordance with the addendum to IEC 60027-2, IEE, and ISO standards.
Our reports do not use the kibi, mebi, gibi terminology. Instead, our reports use the correct terminology of KB, MB, GB, and TB.
Edgecast CDN