Report Builder

Applies To:

HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.

HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.

ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

Report Builder is designed to generate customized reports that contain CDN usage data relevant to your business needs. It allows you to:

Define a report by selecting a custom time period, delivery platform(s), and the set of data that will be included in the report.
Export report data as a comma-separated values (CSV) or JSON file.
Schedule email delivery of report data as a CSV or JSON attachment.

Use our Grafana data source plugin, which is called Verizon Media Platform Analytics, to create queries through which you may gain insight into historical and near real-time CDN performance.

The primary function of these reports is to assess performance and gather data on CDN usage. These reports should not be used for billing purposes.

Please contact your CDN account manager to activate Report Builder.

Data Retention

Report Builder retains your data for at least 7 days. Your plan determines whether log data will be stored for a longer time period (i.e., 7, 30, or 45 days).

Contact your account manager to upgrade your plan.

Quick Start

Export report data through the following steps:

Create a report that identifies the time period, the delivery platform, and the type of data (i.e., metrics and dimensions) that will be reported.
Click Download.
Optional. Save the report for future use by clicking Save.

Key Terms

Definitions for key terms are provided below.

Term	Description
CSV / JSON	Report Builder can generate a file that contains report data that matches the criteria (i.e., time period, time interval, delivery platform, metrics, and dimensions) defined in a report. The format for this file may either be: CSV: Comma-separated values. Reports in CSV format contain a header line that identifies the metric or dimension corresponding to each column. Each subsequent row provides statistical data for each unique combination of dimensions. String values may be enclosed within double-quotation marks. JSON: JavaScript Object Notation. Reports in JSON format contain an array of objects. Each object contains key-value pairs for each unique combination of dimensions. Generate reports using JSON format via our REST API or by scheduling report delivery via email.
Record	A record is represented by a line in a CSV file or an object within a JSON file. A record contains report data that identifies each unique combination of dimensions. A report may be manually assigned up to two dimensions (e.g., Country Code and Edge CNAME). A record will only be included within a report when at least one metric is set to a non-zero value. Missing records is not an indicator of data loss. If a time interval has been defined, then the Time dimension will be automatically included in the report. This may cause the report to contain up to three dimensions. Learn more. For example, if a report has been assigned the Country Code and Edge CNAME dimensions, then it may contain the following records: Requests from the US to cdn.example.com. Requests from Canada to cdn.example.com. Requests from the US to cdn2.example.com.
Fields	A field is a generic term for: Metrics: Metrics measure the rate or the total number of times that a particular attribute occurred over a given record. View metric definitions. Dimensions: Dimensions describe an attribute of a request and are typically used to correlate the desired set of requests with metrics. View dimension definitions. The first line in a CSV file is a comma-separated list of fields that define how data is organized within the CSV.

Term

Description

CSV / JSON

Report Builder can generate a file that contains report data that matches the criteria (i.e., time period, time interval, delivery platform, metrics, and dimensions) defined in a report. The format for this file may either be:

CSV: Comma-separated values. Reports in CSV format contain a header line that identifies the metric or dimension corresponding to each column. Each subsequent row provides statistical data for each unique combination of dimensions.

String values may be enclosed within double-quotation marks.
JSON: JavaScript Object Notation. Reports in JSON format contain an array of objects. Each object contains key-value pairs for each unique combination of dimensions.

Generate reports using JSON format via our REST API or by scheduling report delivery via email.

Record

A record is represented by a line in a CSV file or an object within a JSON file. A record contains report data that identifies each unique combination of dimensions. A report may be manually assigned up to two dimensions (e.g., Country Code and Edge CNAME).

A record will only be included within a report when at least one metric is set to a non-zero value. Missing records is not an indicator of data loss.

If a time interval has been defined, then the Time dimension will be automatically included in the report. This may cause the report to contain up to three dimensions.
Learn more.

For example, if a report has been assigned the Country Code and Edge CNAME dimensions, then it may contain the following records:

Requests from the US to cdn.example.com.
Requests from Canada to cdn.example.com.
Requests from the US to cdn2.example.com.

Fields

A field is a generic term for:

Metrics: Metrics measure the rate or the total number of times that a particular attribute occurred over a given record.

View metric definitions.
Dimensions: Dimensions describe an attribute of a request and are typically used to correlate the desired set of requests with metrics.

View dimension definitions.

The first line in a CSV file is a comma-separated list of fields that define how data is organized within the CSV.

Time

A report's date range determines the set of data that will be included in it, while a report's granularity (i.e., time interval) determines the scope of each individual record.

Time Periods

Each report must be assigned a relative or fixed time period via the Date Range option. This time period defines a start and end date/time for the data that will be included when generating report data.

Definitions for each available time period are provided below.

Time Period	Start Date/Time	End Date/Time
Today	Current date at 12:00:00 AM (UTC)	Current date/time (UTC)
Yesterday	Yesterday at 12:00:00 AM (UTC)	Today at 12:00:00 AM (UTC)
Last 7 days	A week ago at the current time (UTC)	Today at the current time (UTC)
Last 30 days	30 days ago at the current time (UTC)	Today at the current time (UTC)
Last 45 days	45 days ago at the current time (UTC)	Today at the current time (UTC)
This Month	The 1st of the current month at 12:00:00 AM (UTC)	Current date/time (UTC)
Last Month	The 1st of the previous month at 12:00:00 AM (UTC)	The first day of the current month at 12:00:00 AM (UTC)
Custom Range	The start date at 12:00:00 AM (UTC)	The day after the end date at 12:00:00 AM (UTC)

A request will be included in the report when it is completed at or after the start date/time and before the end date/time.

Time Intervals

If a time interval (e.g., 5 minutes, hourly, or daily) has been selected via the Granularity option, then the Time dimension will be automatically included upon generating a report. In which case, each record covers a single time interval. Time intervals are described below.

Time Interval	Start Time	End Time
5 Minutes	Time dimension (UTC)	Time dimension (UTC) + 5 minutes
Hourly	Time dimension (UTC)	Time dimension (UTC) + 1 hour
Daily	12:00:00 AM (UTC)	The subsequent day at 12:00:00 AM (UTC)
Weekly	Monday at 12:00:00 AM (UTC) The first record's start time is the report's start date at 12:00:00 AM (UTC)	Monday of the following week at 12:00:00 AM (UTC) The last record's end time is the report's end date at 12:00:00 AM (UTC).
Monthly	The 1st of the month at 12:00:00 AM (UTC). The first record's start time is the report's start date at 12:00:00 AM (UTC)	The 1st of the subsequent month at 12:00:00 AM (UTC) The last record's end time is the report's end date at 12:00:00 AM (UTC).

The Time dimension always indicates a record's start time.

Key information:

If a time interval is not defined by the Granularity option, then each record covers the entire report's time period.
The set of available time intervals varies according to the selected time period. For example, a report for less than 7 days will allow you to select a five minute, hourly, or daily time interval, while a report for the last 45 days only allows daily, weekly, or monthly time intervals.

This behavior is due to our data retention policy.
A record will only be included within a report when at least one metric is set to a non-zero value. Missing records are not an indicator of data loss.
A request will be included in a record when it is completed at or after the start time and before the end date/time.

Filters

Filter a report to only include records that contain a dimension that matches a specific condition. Specify a condition by setting an operation and the value to which it will be applied.

Operation	Description
Contains	Checks whether the dimension contains the specified value. View example. This example assumes the following configuration: Edge CNAME Contains example The above filter will include records for the following edge CNAMEs: cdn.example.com cdn.example2.com example.cdn.com example2.cdn.com It will exclude records for the following edge CNAMEs: cdn.random.com exam.pleasant.com
Does Not Contain	Checks whether the dimension does not contain the specified value. View example. This example assumes the following configuration: Edge CNAME Does Not Contain example The above filter will include records for the following edge CNAMEs: cdn.random.com exam.pleasant.com It will exclude records for the following edge CNAMEs: cdn.example.com cdn.example2.com example.cdn.com example2.cdn.com
Does Not End With	Checks whether the dimension does not end with the specified value. View example. This example assumes the following configuration: Edge CNAME Does Not End With net The above filter will include records for the following edge CNAMEs: cdn.example.com cdn.example.org cdn.example.io It will exclude records for the following edge CNAMEs: cdn.example.net cdn2.example.net
Does Not Equal	Checks whether the dimension is not an exact match for the specified value. View example. This example assumes the following configuration: Edge CNAME Does Not Equal cdn.example.com The above filter will include records for the following edge CNAMEs: cdn2.example.com cdn.example.org cdn.example.io It will exclude records for the following edge CNAME: cdn.example.com
Does Not Match	Checks whether the dimension does not match the RE2-compatible regular expression. View example. This example assumes the following configuration: Edge CNAME Does Not Match cdn\.example\.com The above filter will include records for the following edge CNAMEs: cdn2.example.com cdn.example.org cdn.example.io It will exclude records for the following edge CNAME: cdn.example.com
Does Not Start With	Checks whether the dimension does not start with the specified value. View example. This example assumes the following configuration: Edge CNAME Does Not Start With cdn The above filter will include records for the following edge CNAMEs: www.example.com sales.example.org It will exclude records for the following edge CNAMEs: cdn.example.com cdn2.example.com
Ends With	Checks whether the dimension ends with the specified value. View example. This example assumes the following configuration: Edge CNAME Ends With net The above filter will include records for the following edge CNAMEs: cdn.example.net cdn2.example.net It will exclude records for the following edge CNAMEs: cdn.example.com cdn.example.org cdn.example.io
Equals	Checks whether the dimension is an exact match for the specified value. View example. This example assumes the following configuration: Edge CNAME Equals cdn.example.com The above filter will include records for the following edge CNAME: cdn.example.com It will exclude records for the following edge CNAMEs: cdn2.example.com cdn.example.org cdn.example.io
Greater Than	Checks whether the dimension is greater than the specified value. View example. This example assumes the following configuration: HTTP Status Code Greater Than 299 The above filter will include records whose status code is 300 or higher. It will exclude records whose status code is 1xx or 2xx.
Greater Than or Equal To	Checks whether the dimension is greater than or equal to the specified value. View example. This example assumes the following configuration: HTTP Status Code Greater Than or Equal To 300 The above filter will include records whose status code is 300 or higher. It will exclude records whose status code is 1xx or 2xx.
In	Checks whether the dimension is an exact match for one or more value(s) selected from a list.
Less Than	Checks whether the dimension is less than the specified value. View example. This example assumes the following configuration: HTTP Status Code Less Than 300 The above filter will include records whose status code is 1xx or 2xx. It will exclude records whose status code is 300 or higher.
Less Than or Equal To	Checks whether the dimension is less than or equal to the specified value. View example. This example assumes the following configuration: HTTP Status Code Less Than or Equal To 299 The above filter will include records whose status code is 1xx or 2xx. It will exclude records whose status code is 300 or higher.
Like	Checks whether the dimension matches the specified pattern. Use the following wildcards when defining this pattern: _: Use an underscore to match exactly one character. %: Use a percent sign to match zero or more characters. View example. This example assumes the following configuration: Edge CNAME Like %.example.com The above filter will include records for the following edge CNAMEs: cdn.example.com cdn2.example.com www.example.com It will exclude records for the following edge CNAMEs: cdn.example.org cdn.example.io
Matches	Checks whether the dimension matches a RE2-compatible regular expression. View example. This example assumes the following configuration: Edge CNAME Matches cdn\.example\.com The above filter will include records for the following edge CNAME: cdn.example.com It will exclude records for the following edge CNAMEs: cdn2.example.com cdn.example.org cdn.example.io
Not In	Checks whether the dimension does not match any of the values selected from a list.
Not Like	Checks whether the dimension does not match the specified pattern. Use the following wildcards when defining this pattern: _: Use an underscore to match exactly one character. %: Use a percent sign to match zero or more characters. View example. This example assumes the following configuration: Edge CNAME Not Like %.example.com The above filter will include records for the following edge CNAMEs: cdn.example.org cdn.example.io It will exclude records for the following edge CNAMEs: cdn.example.com cdn2.example.com www.example.com
Starts With	Checks whether the dimension starts with the specified value. View example. This example assumes the following configuration: Edge CNAME Starts With cdn The above filter will include records for the following edge CNAMEs: cdn.example.com cdn2.example.com It will exclude records for the following edge CNAMEs: www.example.com sales.example.org