Update and technical manual for the streaming video platform: user services

The Media Control Center uses various levels of tabs to organize CDN settings and tools into categories. The top level tabs are known as navigation tabs. These tabs provide access to pages that allow you to administer your CDN configuration and view CDN reports for traffic performed on your account.

Note: If you have not purchased a particular platform, then the corresponding navigation tab will either be disabled or hidden.

Note: User rights also determine which navigation elements within the MCC will be available. For example, if a user has not been granted the Flash privilege, then the Flash tab will be disabled for that user.

The following illustration indicates where you can find the navigation tabs within the MCC.

MCC Home Page (Shown with Highlighted Navigation Tabs)

Hovering over a navigation tab will open a fly-out menu containing links for the pages associated with that category. This fly-out menu allows you to quickly navigate to the desired page.

HTTP Large Tab (Shown with a Fly-Out Menu)

Sub Navigation Bar

Each tab, with the exception of the Home page, contains a sub navigation bar. This sub navigation bar is a collection of links for the different pages associated with the selected tab. The default page that will appear when you click on a navigation tab is the page associated with the first link in the sub navigation bar.

The following illustration indicates where the sub navigation bar can be found.

HTTP Large Tab (Shown with a Highlighted Sub Navigation Bar)

Side Navigation Bar

Certain pages that are accessed from the sub navigation bar contain many diverse options. As a result, each set of options must be placed on its own page. In order to accommodate these pages, a side navigation bar is included to provide access to them.

The following illustration indicates where the side navigation bar can be found.

Query-String Caching Page on the HTTP Large tab (Shown with a Highlighted Side Navigation Bar)

Top Level Navigation

The final set of navigation links appear in the upper-right hand corner of the MCC. A brief description is provided below for each link.

Name

Description

Home

This link will display the home page for the MCC. The home page is the default page that appears when the MCC is first loaded. It can also be displayed by clicking on the Home tab.

My Settings

This link allows you to view/modify your profile. In addition to defining your personal information, you can also change your password and sign up for e-mail notifications.

Language

This link allows you to set the MCC’s language for the current web browser. Keep in mind that the selection of a different language takes place immediately.

Support

This link provides access to a library of technical documents. Follow the “Submit Support Request”link to fill out a form through which you can submit a request for technical support.

Logout

This link will immediately log you out of the MCC.

Note: Company and user information is provided next to these links. This information includes the e-mail address associated with the current user, your company name, and your company’s MCC account number. The MCC account number is especially important, since it is used by our CDN URLs.

The following illustration indicates where these top-level navigation links can be found.

Top Level Navigation Bar

 Support Services

In addition to the MCC, which provides a central place through which you can perform CDN configuration, we offer the following additional support services:

·        Create, manage, and review your company’s technical support cases.

·        Access a Knowledge Base that contains technical information on how different aspects of the CDN work and how to troubleshoot issues.

These services are provided through a separate portal that can be accessed through the following URL:

·       https://members.gravlab.com/

Service-Now Home Page

Access to these support services is limited to the users that have been created for your customer account in the MCC. In other words, only MCC users can create, review, and manage your company’s technical support cases. By restricting access to your technical support cases, you can ensure that only authorized users will be privy to your sensitive information.

Key information about the Service-Now (SNC) support center:

·       Login: A user will need to provide their MCC user account (i.e., e-mail address) and password when logging in to SNC.

·       User Account Creation/Modification: It may take up to 15 minutes before a new or modified user account can be used to log in to SNC. The types of user account modifications that can temporarily affect your access to SNC are changes made to your e-mail address or password.

User Accounts

Overview

The MCC provides administrative control over who can access it and the actions a user can perform once access has been granted. By allowing varying levels of MCC access, different types of users across the organization can have access to the MCC in a controlled and secure manner.

Authorized administrators can manage user accounts from the Admin tab of the MCC. Additionally, any user can modify their personal settings. This chapter will discuss how administrators can manage user accounts and how an individual user can update his profile information.

Admin Tab

Privileges

Access to the Media Control Center (MCC) is limited to the set of users that have been created for your organization. The MCC users for your organization are assigned a set of privileges by a MCC administrator. These privileges determine the level of access that a user will have when he/she logs into the MCC.

Note: Privileges only affect actions performed within the MCC. For example, although a user may not have permissions for the Flash Media Streaming platform, he/she may still upload new content to the appropriate origin server and stream on-demand content through your account.

 If a platform or service has not been activated on your customer account, then the corresponding privileges will either be hidden or disabled and you will not be allowed to grant them to your users. For example, the Token Auth and Rules Engine privileges are hidden in the following illustration, because the Token-Based Authentication and the HTTP Rules Engine features have not been granted to that customer account. For more information, please contact your CDN account manager.

Partial List of Privileges (Shown without the Token Auth and the Rules Engine Privileges)

Privileges are based on the user interface of the MCC. This means that each tab (e.g., Home, Media Manager, HTTP Large, etc.) and the sub navigation pages associated with those tabs (e.g., HTTP Large, Customer Origin, My Edge, etc.) have been associated with a privilege. These privileges are laid out according to that hierarchy. This means that sub navigation privileges are indented directly below the privilege corresponding to the tab on which it can be found. In addition to providing a visual cue as to the purpose of a particular privilege, this arrangement serves a functional purpose. The sub-privileges associated with a particular platform are automatically marked or cleared when you toggle the status for the tab (e.g., HTTP Large, HTTP Small, ADN, etc.) associated with it. Additionally, since you must have access to a tab before you can view a page pertaining to it, marking a sub-privilege will automatically also mark the privilege corresponding to the parent tab.

Note: Parent privileges only control whether the corresponding tab will be enabled or disabled. For example, if the HTTP Streaming privilege is enabled and all of its sub-privileges are disabled, then access will be allowed to the HTTP Streaming tab but you will be unable to access any Smooth Streaming settings or resources.

Note: The ability to view or administer a particular platform or feature depends on whether you have purchased it.

Note: A user’s ability to modify his/her own basic profile settings is not controlled by privileges. However, only users that have been granted the Users privilege can assign privileges or define a user’s custom ID.

Note: For more information, please refer to Appendix B: Privileges.

User Account Administration

The ability to administer MCC users is determined by the Users privilege, which is a sub-privilege of the Admin privilege. Once a user has been granted this privilege, he/she will be able to view a list of your organization’s users from the Users page of the Admin tab. In addition to being able to view a list of users, it allows that user to view, modify, or even delete individual users.

Tip: If you are looking for a more efficient way to find a particular user, try using the Search option on the Users page. The results of such a search will display all users whose first name, last name, or e-mail address contain the specified search term.

Note: Although a user that has been granted the Users privilege can administer users, he/she will not be able to delete his/her own account or the primary MCC account.

Creating a User Account

A user account can be created by clicking Add User from the Users page, which can be found on the Admin tab. When creating a user, you must fill out the following fields: First Name, Last Name, and E-Mail/Username. Additionally, you should only grant those privileges that you deem necessary for that particular user.

Reminder: The ability to create a user is determined by the Users privilege, which is a sub-privilege of Admin.

Once a user has been created, an e-mail will be sent to the e-mail address associated with the new user account. This e-mail will indicate that a MCC user account has been created and it will provide a user account activation link. A new user will need to follow the user account activation link where the user will be prompted to enter their e-mail address. After which, the new user will need to specify and confirm a six character password. The new account will be activated upon successfully setting a password.

Reminder: All MCC users also have access to the Service-Now support center. This support center provides the capability to view/update technical support cases and access a Knowledge Base.

Modifying a User Account

Any user that is listed on the Users page of the Admin tab can be modified. Simply click on the  that appears next to the desired user. The Edit User page will display a form that is filled out with that user’s properties. Once you have made the desired changes, click Save to update that user’s account.

Note: Changes made to a user’s privileges do not fully take effect until the next time that user logs in to the MCC. If the user is currently logged in and would like for his/her new privileges to take effect, you should suggest that he/she log out and then log back in to the MCC.

Reminder: The ability to modify a user’s settings or privileges is determined by the Users privilege, which is a sub-privilege of Admin.

Password Expiration

A password expiration policy defines the maximum number of days that can elapse before a password must be changed. This policy can be defined on a per user basis. When defining a user’s password expiration policy, keep in mind the following:

·        A user’s password expiration policy is defined by the Password Expiration option. This option can be set when modifying a user account.

·        The units used by the Password Expiration option are days.

·        The Password Expiration option must be set to a value between 0 and 999 or it can be left blank.

·        Setting the Password Expiration option to 0 will cause that user’s password to never expire. This type of configuration is highly discouraged.

·        Setting the Password Expiration option to blank will assign a default password expiration policy to that user. This default password expiration policy can be updated at any time by your CDN account manager.

To set a user’s password expiration policy

1.      From the Users page, click on the Edit ( ) icon that appears next to the desired user.

2.      In the Password Expiration option, specify one of the following:

·       0: If you do not wish for a user’s password to expire, then you should set this option to zero.

·       Password Change Interval: Specify the maximum number of days that can pass before the selected user is forced to change their password.

Deleting a User Account

Any user, except for the primary administrator and the current user, can be deleted from the Users page. Simply click on the  that appears next to the desired user.

Reminder: The ability to delete a user is determined by the Users privilege, which is a sub-privilege of Admin.

Custom User ID

Each user can be assigned a customized ID. This custom ID can be tailored to match an internal naming convention. For example, the custom ID for each user could be their Active Directory user name. A custom user ID can only be configured when creating a user or when modifying that user’s settings from the Users page in the MCC. As a result, only users that have been granted the Users privilege can modify a user’s custom ID.

Note: Although a user cannot modify their own custom ID from the General Info page, they can view it from that page.

Updating Profile Settings

Any MCC user can view and/or modify his/her own profile settings, such as name, e-mail address, address information, and phone number. A user can update his/her account settings by clicking My Settings from the upper-right hand corner of the MCC. The General Info page will display a user’s current profile information. If a user would like to update his/her profile, then he/she can click Edit. The options listed on the General Info page can now be modified. Update the desired settings and then click Save.

Note: The E-Mail/Username option serves a dual purpose. It defines a user name account that will be used to access MCC and it determines where a variety of e-mail notifications will be sent. 

Note: Although an administrator that has been granted both the Admin and Users privileges can modify any user’s settings, only a particular user can determine whether he/she would like to receive e-mail notifications or change his/her password.

Reminder: The Custom Id option can only be updated when modifying a user’s settings from the Users page.

Web Services REST API token

The Web Services REST API token is a value that identifies and authenticates a user when performing a call to the Web Services REST API. It is recommended that a user take the appropriate precautions to prevent this value from being disseminated. For example, a user should never leave a WCC session unattended.

If you suspect that a token value has been compromised, then you should perform the following steps:

1.      Generate a new primary token.

2.      Update any applications or scripts that rely on the old Web Services REST API token.

3.      Distribute your applications or scripts to the appropriate entities and/or locations.

4.      Delete the backup Web Services REST API token.

Best Practices: Web Services REST API Token Security

Web Services REST API tokens should be treated like any other security credential or password. It is paramount to keep this type of token as secure as possible. We have observed incidents in which customers lost control of their Web Services REST API token and then experienced unauthorized access on their account.  

The following precautions are recommended:

·        Ensure that a Web Service REST API token is not shared within or outside of your organization. For example, they should not be inadvertently posted on an online support form.

·        Periodically change your Web Service REST API token.

·        Perform general administrative security tasks on a regular basis. These tasks include:

§  Remove old user accounts.

§  Change passwords on a regular basis.

§  Reminder users to use complex passwords.

Password

A user can also change his/her own password by clicking Change Password from the General Info page. The Change Password page will appear. A user will need to specify his/her old password, a new password, and then confirm that new password. Click Save to apply the change to your password.

Note: The minimum length for a password is 6 characters.

Log Files

Overview

A record of basic CDN activity can be archived as an asset in your CDN storage account or on an external server. This record is known as a raw log file. The following types of CDN activity/statistics are recorded in raw log files:

·        Bandwidth usage

·        Traffic statistics

·        Cache

·        Storage usage

Additionally, supplemental information is stored for each action that takes place. For example, the CDN and edge CNAME URLs associated with each request is also stored in our raw log files. Our reporting tools rely on this data to provide reports and graphs for the different types of CDN activity that took place for your account. For example, reports can be generated for the total amount of traffic generated by a particular region for your account, the hourly bandwidth for a particular platform, the amount of data transferred per platform, and cache hit statistics.

Log files are collected approximately every 10 minutes from around the world. If a server is unable to provide log file information at a given time, then the server will deliver it when communication resumes.

Note: Activity in a log file is time-stamped using GMT notation. This allows you to keep track of when an event took place, regardless of the time zone where it was recorded.

Log File Naming Convention

The following naming convention is used to name raw log files:

·       Platform_xxxx_YYYYMMDD_nnnn.log.gz

As you may be able to tell from the above file naming convention, the following two file name extensions are assigned to raw log files:

·       Gz: The.gz file name extension indicates that the raw log data has been compressed using the gzip file format. A software application is required to decompress this file type.

·       Log: The .log file name extension indicates that the text file corresponds to a log file. Although this file type can be opened with a text editor, you may wish to open it using a third-party reports &analytics tool.

A description is provided for the different elements in the log file name.

Variable

Description

Platform

This term represents the CDN platform for which activity was logged. Valid values for this term are listed below:

·       wpc: HTTP Large platform (Includes the Smooth Streaming service.)

·       wac: HTTP Small platform

·       adn: Application Delivery Network platform

·       fms: Flash Media Streaming platform

·       wms: Windows Media Streaming platform

xxxx

This term represents your CDN account number (e.g., 0001). This account number can be viewed from the upper-right hand corner of the MCC.

YYYY

This term represents the four digit year on which the log file was generated by a CDN server.

MM

This term represents the two digit month on which the log file was generated by a CDN server.

DD

This term represents the two digit day on which the log file was generated by a CDN server.

nnnn

This term is replaced by a four digit number that ensures that all of the log files generated for the current day are assigned a unique name.

Log File Storage

Basic log data is automatically archived on our servers. As a result, you will always be able to access basic information about your CDN activity data through the Core Reporting module. Core reports are available from the Reports tab of the MCC. However, you may wish to store more detailed log information or use a third-party tool to analyze your log data. For this reason, we allow you to store log information on a CDN origin server and/or to deliver them directly to your servers.

Important: Log files are not stored on CDN or customer storage by default. If you would like to retain this data, make sure to enable log file archival for CDN and/or customer storage.

Important: If you are unable to enable the storage and delivery of raw log files on a platform, it is due to the fact that CDN traffic for that platform is being tracked through a logless system. Platforms that have been assigned to a logless system will also be unable to take advantage of other log-dependent features, such as the following EC360 Reporting modules: Advanced Content Analytics and Edge Performance Analytics. For more information, please contact your CDN account manager.

CDN Storage (CDN Origin Server)

Log files can be automatically archived to a CDN origin server. Enabling log file archival will store log files for the selected platforms in a folder called “Logs”on your CDN origin server. You can access log data stored on a CDN origin server through your preferred FTP client or through the embedded FTP client, which can be found on the File Management page of the Media Manager tab in the MCC.

Log data storage options can be configured from the Company Settings page of the Admin tab in the MCC. In addition to being able to turn it on/off on a per platform basis, you may also determine how long log files will be retained on the CDN origin server.

Note: Keep in mind that your account will be billed for the amount of storage space used on a CDN origin server. For a detailed explanation of account billing, please contact your CDN account manager.

To configure log storage options

1.      Navigate to the Company Settings page of the Admin tab in the MCC.

2.      Perform one of the following:

·        If you do not wish to archive log files on to CDN storage, then you should select the Log storage is turned off option.

·        If you would like to archive log files, then you should perform the following steps:

                                                                       i.     Make sure that the Log storage is turned on option is selected.

                                                                      ii.     Mark each platform for which you would like to store log data.

                                                                     iii.     Clear each platform for which log data will be discarded.

                                                                     iv.     In the Please keep log files for option, you should select the amount of time that the log files for each selected platform should be kept. If you choose “unlimited,”then log files will not be automatically deleted from the CDN origin server.

3.      Click Update to save your changes.

External Server Storage

Log files can be archived using the FTP protocol to an external server of your choosing. Additionally, you can choose to be notified by e-mail if a log file is not successfully delivered to your server.

To configure log file delivery settings

1.      Navigate to the Company Settings page of the Admin tab in the MCC.

2.      Perform one of the following:

·        If you would like to archive log files to an external server, then you should make sure that the Enabled option is selected from the FTP Delivery Settings section.

·        If you do not wish to archive log files to an external server, then you should make sure that the Disabled option is selected from the FTP Delivery Settings section. Skip to the last step.

3.      In the Notification E-mail option, type the e-mail address to which an e-mail will be sent if a log file is not successfully delivered to your server.

4.      In the Hostname option, type the hostname or IP address of the server where log files will be archived. Make sure that you do not to include protocol information (e.g., http://, https://, ftp://, etc.).

5.      In the Directory Path option, type the path to the folder where log files will be archived. This path starts at the root folder of the server specified in the previous step. Make sure to start this path with a forward slash (e.g., /Logs).

6.      In the Username option, type the name of the user that has FTP access to your server and can read/write to the specified folder. In the Password option, you should type the password associated with the specified user account.

7.      Click Update to save your settings.

Log File Format

As previously mentioned, raw log files are generated on a regular basis by our servers around the world. These servers will generate a raw log file for each platform for which they audited CDN activity. The log data generated for each platform varies due to the nature of the activity being recorded (e.g., HTTP GET requests vs. streaming). As a result, the log file format is different for each platform. This section will describe the log file format for HTTP platforms, Flash Media Streaming, and Windows Media Streaming platforms.

HTTP Platforms

A single log file format is used to record CDN activity for the HTTP Large (including Smooth Streaming), HTTP Small, and Application Delivery Network platforms. This format can be customized, so that you can easily integrate CDN log data with your third-party report generation application. In addition to providing information on how to customize the log file format, we describe the default log file format and the fields that can be included in a log file. This information will help you get acquainted with the type of log information that you can leverage into a third-party report.

Default Log File Format

The default format used to record HTTP activity in a raw log file is similar to an extended W3C log. An extended W3C log file is an ASCII text-based format defined by W3C and used as the default log file format by IIS. The main differences between our default log file format and the extended W3C log format are the following:

·        Our servers record date and time as a single field using Unix time (a.k.a. POSIX time or Unix epoch) in our log files. A standard extended W3C log file format, on the other hand, records date and time as two separate fields using the GMT time zone. The date and time format used by the extended W3C log file format is described below.

§ Date format (Extended W3C): YYYY-MM-DD

§ Time format (Extended W3C): HH:MM, HH:MM:SS, or HH:MM:SS.S.

·        Our servers record an additional field where the account number associated with the customer is reported.

·        Our servers record an additional field called “x-ec_custom-1″that can be used to log custom information. The information that will be logged by this field is determined by an HTTP Rules Engine feature.

The following list indicates the default order in which data is recorded in a raw log file:

·        Date/Time (timestamp)

·        Time Taken (time-taken)

·        Client IP Address (c-ip)

·        File Size (filesize)

·        Edge Server IP Address (s-ip)

·        Edge Server Port (s-port)

·        HTTP Status (sc-status)

·        Bytes Sent (sc-bytes)

·        HTTP Method (cs-method)

·        Request URL (cs-uri-stem)

·       

·        Remote Server Time Taken (rs-duration)

·        Remote Server – Bytes Sent (rs-bytes)

·        Referrer (c-referrer)

·        User Agent (c-user-agent)

·        Customer Account Number (customer-id)

·        Custom Log Field 1 (x-ec_custom-1)

Note: For a description of a particular field, please refer to the Log File Field Definition topic.

Restoring the Default Log File Format Configuration

If you have customized how HTTP activity is recorded in our log files and would like to restore the default log file format, then you will need to make sure that the Log Format Settings section of the Raw Log Settings page is configured as follows:

·       Base log file format: The Default format option should be selected.

·       Format the date/time field using: The Unix time (Unix Epoch) option should be selected.

·       Add this custom field to the log file: This option should be marked and set to “x-ec_custom-1.”

·       Remove the content access point from the URL: This option should be cleared.

Your log file format settings should look like the following illustration:

Default Log File Format Settings

Log File Field Definition

Each raw log file consists of a set of fields that describe HTTP activity data. The exact set of fields that will be included in your raw log file depends on whether you have configured your raw log file to use the default or combined log file format. Additionally, you can also choose whether a custom field will be included in the raw log file and the header information that will be included. For more information, please refer to the Custom Log File Format topic.

The fields that can be defined in a raw log file are listed and described below.

Note: If you are using the combined log format, then the field names will not be reported as a header in each raw log file. For information on the order in which data will be recorded, please refer to the Base Log File Format section of the Custom Log File Format topic.

Field

Name

Applicable Log Format(s)

Description

Default

This field always reports “-.”

c-ip

Client IP Address

Default
Combined

The IP address of the client that made the request to the server.

c-referrer

Referrer

Default
Combined

The URL of the site from which the request originated. This field will typically be set to “-“for the HTTP Small and the ADN platforms.

cs-method

HTTP Method

Default

The type of action that was requested. This field is reported according to the HTTP method (i.e., GET, HEAD, POST, PUT, and DELETE) that was used to make the request.

cs-uri-stem

Request URL

Default
Combined

The URL for the CDN content that was requested, posted, or deleted.

c-user-agent

User Agent

Default
Combined

The user agent that the client used to perform CDN activity.

customer-id

Customer Account Number

Default

The customer account number through which the request was processed.

filesize

File Size

Default
Combined

The size of the requested asset in bytes.

rs-bytes

Remote Server Bytes Sent

Default

The number of bytes that an origin server sent to an edge server.

rs-duration

Remote Server Time Taken

Default

The length of time, in milliseconds, that it took the origin server to process the requested action. This field does not take into account network time.

sc-bytes

Bytes Sent

Default

The number of bytes that the edge server sent to the client.

sc-status

HTTP Status

Default
Combined

The cache status and the HTTP status code returned by either an origin server or an edge server. For more information on cache statuses, please refer to the Appendix A: Cache Status Codes.

s-ip

Edge Server IP Address

Default

The IP address associated with the edge server that processed the request.

s-port

Edge Server Port

Default

The port number associated with the edge server that processed the request.

timestamp

Date/Time

Default
Combined

The date and time (GMT) at which an edge server delivered the requested content to the client. The format in which date/time is reported is determined by your log file format settings. By default, this field is reported in Unix time. For more information, please refer to the Default Log File Format and Custom Log File Format topics.

time-taken

Time Taken

Default

The length of time, in milliseconds, that it took to process the requested action. For example, if the asset had to be retrieved from an origin server, then this field indicates the number of milliseconds it took to read the asset from the origin server. This field does not take into account network time.

x-ec_custom-1

Custom Log Field 1

Default

This is a custom field that can report request and response headers. This field will only appear in a raw log file when the Add this custom field to the log file option is marked. The type of headers that will be logged is determined by the rules that have been associated with each platform. For more information, please refer to the Custom Field section of the Custom Log File Format topic.

Custom Log File Format

The format in which data generated for CDN activity over the HTTP protocol is stored in a raw log file is determined by the settings defined in the Log Format Settings section of the Raw Log Settings page. These log file formatting settings allow you to:

·        Define the base log file format

·        Define the date/time format

·        Determine whether a custom field will be included

·        Determine whether the content access point will be logged

Important: Typically, data mining tools require a consistent log format when analyzing data over a period of time. If you plan on using a data mining application on your log data, then it is key to keep changes to your log file to a minimum. Please contact your CDN account manager before making any changes.

Base Log File Format

The base log file format determines the basic format that will be used to record HTTP activity in a raw log file. Once you have selected a base log file format, you can adjust other log file format settings (e.g., date/time format) to achieve your optimal log format. When choosing a base log file format, you will need to choose between the following two log file formats:

·       Default format: The default log file format is similar to an extended W3C log file format. This type of format is described in the Default Log File Format topic.

·       Combined format: A combined log file format is similar to the default log file format used by Apache web servers. The following list of fields indicates the type of data and the order in which it is recorded in a raw log file:

§  Client IP Address

§  Client Identification

§  Client User Name – HTTP Authentication

§  Date/Time

§  Request URL

§  Request Status Code

§  File Size

§  Referrer

§  User Agent

§  Custom Log Field 1

Note: Unlike the default log file format, the combined format does not provide a list of field headers in each raw log file.

Note: By default, the Client Identification and the Client User Name – HTTP Authentication fields report a dash (i.e., -) for each request.

Note: Custom Log Field 1 will only be reported if custom logging is turned on when the CDN activity being reported takes place.

Date/Time Format

A CDN server records the date and time at which it processed the request for an asset in a log field called “timestamp.”The format in which data is recorded in this field can be customized in one of the following ways:

·       Unix time (Unix Epoch): Date and time can be recorded in the timestamp field as the number of seconds since Unix time (a.k.a. POSIX time or Unix epoch). Unix time starts on 1970-01-01 at 00:00:00 GMT.  For example, if the timestamp field reports “1294401600”then the request was processed on 1/07/2011 at 12:00:00 GMT. This is the default format for the timestamp field.

·       Custom date/time (Default format): If the base log file format is set to Default format, then selecting the Custom date/time format option will record date and time in the timestamp field using the following format: YYYY-MM-DD hh:mm:ss (e.g., 2012-01-07 12:00:00). Each date/time variable is defined below.

§ YYYY: Indicates a year in the Gregorian calendar using a four digit number (e.g., 2012).

§ MM: Indicates a month of the year between 01 (January) and 12 (December).

§ DD: Indicates a day of the month between 01 and 31.

§ hh: Indicates an hour of the day (GMT) between 00 and 24.

§ mm: Indicates minutes between 00 and 59.

§ ss: Indicates seconds between 00 and 59.

·       Custom date/time (Combined format): If the base log file format is set to Combined format, then selecting the Custom date/time format option will record date and time in the timestamp field using the following format: DD/MMM/YYYY:hh:mm:ss +hhhh (e.g., 07/Jan/2011:12:00:00 +0800). Each date/time variable is defined below.

§ DD: Indicates a day of the month between 01 and 31.

§ MMM: Indicates a three letter abbreviation for a month of the year (e.g., Jan).

§ YYYY: Indicates a year in the Gregorian calendar using a four digit number (e.g., 2012).

§ hh: Indicates an hour of the day between 00 and 24.

§ mm: Indicates minutes between 00 and 59.

§ ss: Indicates seconds between 00 and 59.

§ +hhhh: Indicates the hour differential between the time reported and GMT.

Custom Field

By default, a custom field called “x-ec_custom-1″is included in your raw log files. If you have not configured HTTP Rules Engine to log data in this field, then it will always report “-“in your raw log files. However, if you have created a rule that includes the “Custom Log Field 1″feature, then you can log HTTP request and/or response headers in this custom field.

Note: Changing the name of your custom field will not affect whether HTTP request and/or response headers are logged.

Reminder: If you are using the combined log format, then the name associated with your custom log field will not be reported in your raw log file.

If you decide to take advantage of a custom field to log HTTP request and/or response headers, then you will need to create a rule that takes advantage of the “Custom Log Field 1″feature. When configuring the “Custom Log Field 1″feature, you will need to specify each request and response header that you would like to log. A header can be specified using the following syntax:

Header Type

Syntax

Example

Request

%{requestheader}i

%{Accept-Encoding}i

Response

%{responseheader}o

%{Content-Type}o

Note: Before specifying a header, you will need to know whether it is a request (inbound) or a response (outbound) header. This will allow you to add the appropriate identifier (i.e., i or o) to the header variable (e.g., %{Cookie}i or %{Content-Range}o).

If you would like to specify multiple headers, then it is recommended that you use a separator to indicate each header. For example, you could use an abbreviation for each header (e.g., AE: %{Accept-Encoding}i CT: %{Content-Type}o).

Tip: Adding the “Custom Log Field 1″feature to a rule that is set to match “Always”allows you to log all transactions for that platform.

Note: You must create a rule for each HTTP platform for which you would like to log data in the custom field.

If you decide that you do not wish to include a custom field, then you can clear the Add this custom field to the log file option. This will prevent HTTP Rules Engine from logging HTTP request and/or response headers in your log file.

To determine whether header information will be logged

1.      Navigate to the Raw Log Settings page in the MCC. This page can be found in the Company Setting sub-tab of the Admin tab.

2.      Perform one of the following:

·       To log header information:

                                                                       i.     Make sure that the Add this custom field to the log file option is marked. If desired, you can change the name that will be assigned to your custom field. If you changed this setting, then you should click Update.

                                                                      ii.     Navigate to the Rules Engine page associated with the platform for which header information will be logged.

                                                                     iii.     If a rule that takes advantage of the “Custom Log Field 1″feature does not exist, then you will need to create one now. When configuring the “Custom Log Field 1″feature, you will need to specify each request and response header that you would like to log (e.g., %{Accept-Encoding}i and %{Content-Type}o). Save your rule by clicking Add.

                                                                     iv.     Repeat the previous step for each desired platform.

Reminder: Append the appropriate identifier (i.e., i or o) to the header name to indicate whether you would like to log requests (inbound) or responses (outbound).

·       To exclude the custom field from raw log data:

                                                                       i.     Make sure that the Add this custom field to the log file option is cleared. If you changed this setting, then you should click Update.

                                                                      ii.     Navigate to the Rules Engine page associated with the platform for which header information will be logged.

                                                                     iii.     Modify or disable the rule that logs header information into your custom field.

Content Access Point

A content access point is a relative path that starts directly after the CDN domain (e.g., /800001/MyOrigin or /000001). By default, this information is reported in the cs-uri-stem field in the log file. The cs-uri-stem field identifies the asset that was requested by the client. The Remove the content access point from the URL option determines whether this information is reported in that field.

Flash Media Streaming Platform

Each raw log file generated for the Flash Media Streaming platform consists of a set of fields that describe streaming activity. The fields that can be defined in a raw log file are listed and described below.

Field

Name

Description

c-client-id

Client ID

The ID assigned to a client.

c-ip

Client IP Address

The IP address of the client that requested the stream from the server.

c-proto

Connection Protocol

The protocol (i.e., RTMP, RTMPE, RTMPT, or RTMPTE) used to transmit the stream.

c-referrer

Referrer

The URL of the referrer used to link to the stream. This field will typically point to the player used to request the stream.

cs-bytes

Client –Server Data Transferred

The number of bytes transferred from the client to the server.

cs-uri-query

Query String

The query string for the URL to the stream path. This field will typically be set to “-.”

cs-uri-stem

Request URL

The URL to the stream path. This URL does not include the stream name.

c-user-agent

User Agent

The user agent used by the client to play the stream.

date

Event Date

The date when the event took place. The format for this field is YYYY-MM-DD (e.g., 2012-03-01).

·       YYYY: Indicates a year in the Gregorian calendar using a four digit number (e.g., 2012).

·       MM: Indicates a month of the year between 01 (January) and 12 (December).

·       DD: Indicates a day of the month between 01 and 31.

sc-bytes

Server – Client Data Transferred

The number of bytes transferred from the server to the client.

sc-stream-bytes

Server – Client Data Transferred Per Stream

The number of bytes transferred from the server to the client per stream.

Note: This field can report a greater value than the x-file-size field when streaming content that is not encoded in FLV format (e.g., MP3).

s-ip

Server IP Address

The IP address associated with the server that processed the request.

time

Event Time

Identifies the time of the event. The format for this field is hh:mm:ss (e.g., 20:00:00).

·       hh: Indicates an hour of the day (GMT) between 00 and 24.

·       mm: Indicates minutes between 00 and 59.

·       ss: Indicates seconds between 00 and 59.

x-app

Content Access Point

The content access point used to request the stream. The format for this field is the origin identifier followed by your MCC account number. Valid values are listed below.

·       00xxxx: On-Demand Content (CDN Origin Server)

·       80xxxx: On-Demand Content (Customer Origin Server)

·       20xxxx: Live streaming

x-category

Event Category

The category of the event that took place. The more common categories deal with authorization and session values.

x-comment

Comments

The comments associated with the stream.

x-duration

Event Duration

The number of seconds that the stream has played.

x-event

Event Name

The type of access event that was logged. Some of the more common access events are described below.

·       auth-connect: Client connects to the server for the purpose of authentication.

·       connect-pending: Theclient’s connection to the server is pending the authentication of the client.

·       connect: Client connects to the server.

·       filenametransform: A stream has been mapped to a physical location.

·       auth-play: Client plays a stream.

·       play: Client plays a stream.

·       pause: Client pauses the stream.

·       stop: Client stops playing a stream or the stream is no longer being published.

·       disconnect: Client disconnects from the server.

x-file-ext

Filename Extension

The filename extension for the asset generated from the stream. This field is useful for identifying its file format (e.g., FLV, MP4, MP3, etc.).

x-file-length

Stream Length

The length of the stream in seconds.

x-file-name

Filename

The relative path to the asset generated from the stream.

x-file-size

Stream Size

The size of the stream in bytes.

x-sid

Stream ID

The ID assigned to a stream. This ID is unique per client session.

x-sname

Stream Name

The name of the stream.

x-status

Status Code

An event’s status code. Some of the more common status codes are described below.

·       100: Indicates that it is waiting for the application to authenticate.

·       200: Indicates that the event was successful.

·       408: Indicates the stream was stopped because the client disconnected from the stream.

Note: Our logs are based on information logged by our instances of Adobe’s Flash Media Servers. As a result, you can view detailed information on Event Name, Event Category, and Status Codes fields on Adobe’s web site.

Calculating Flash Media Streaming Billing

A raw log file provides event-based data (e.g., Play, Stop, etc.) on the amount of data transferred for each stream. This information can be used to calculate billing data as indicated below.

·       All Connections: Calculate billing data for all connections by finding all log entries where the x-event field is set to Disconnect. Sum the sc-bytes values associated with those entries.

·       Stream-Specific: Calculate billing data on a per stream basis by finding all log entries for the desired session where the x-event field is set to Stop. Sum the sc-bytes values associated with those entries.

Windows Media Streaming Platform

Each raw log file generated for the Windows Media Streaming platform consists of a set of fields that describe streaming activity. The fields that can be defined in a raw log file are listed and described below.

Note: Our logs are based on information logged by our instances of Microsoft’s Windows Media Servers. As a result, you can view detailed information on each of these fields on Microsoft’s web site.

Field

Name

Description

audiocodec

Audio Codec

The audio codec used by the client to decode the audio stream.

avgbandwidth

Average Bandwidth (Client)

The average bandwidth received by the client. This field ignores paused sessions.

c-buffercount

Buffering Count (Client)

The number of times that the client underwent buffering.

c-bytes

Received Bytes (Client)

The number of bytes received by the client. This value does not include the overhead cost of streaming (e.g., TCP/IP).

c-cpu

CPU Type (Client)

The type for the client’s CPU.

c-dns

Server DNS

This field may specify the hostname of the server sending the log. Typically, this field is set to “-.”

channelURL

Multicast URL

The URL to the multicast station file (NSC).

c-hostexe

Host Filename (Client)

The filename of the executable that launched the player.

c-hostexever

Host Version (Client)

The version number of the host that launched the player.

c-ip

IP Address (Client)

The IP address of the client that requested the stream from the server.

c-max-bandwidth

Maximum Bandwidth (Edge Server)

The maximum amount of bandwidth that was streamed at any given time during a session.

c-os

OS (Client)

The client’s operating system.

c-osversion

OS Version (Client)

The version of the client’s operating system.

c-pkts-lost-client

Lost Packets (Client)

The number of ASF data packets sent to the client that were lost and not recovered.

c-pkts-lost-cont-net

Maximum Consecutive Lost Packets

The largest number of consecutive ASF data packets that were lost.

c-pkts-lost-net

Lost Packets (Network Layer)

The number of ASF data packets that were lost on the network layer.

c-pkts-received

Received Packets (Client)

The number of ASF data packets received by the client.

c-pkts-recovered-ECC

Recovered Packets (Network Layer)

The number of recovered ASF data packets that were lost on the network layer.

c-pkts-recovered-resent

Recovered Packets (Resent)

The number of ASF data packets that were recovered either because they were resent through UDP or because they were received out of order.

c-playerid

Player ID (Client)

The globally unique identifier (GUID) assigned to the client’s player.

c-playerlanguage

Player Language (Client)

The language of the client’s player using the corresponding language code.

c-playerversion

Player Version (Client)

The version of the client’s player.

c-quality

Packet Percentage (Client)

The percentage of packets received by the client.

c-rate

Streaming Rate

The rate of streaming as a multiplier of the normal streaming rate.

c-resendreqs

Lost Packet Requests (Client)

The number of requests made by the client to receive lost ASF data packets.

cs(Referer)

Referrer (Client)

The URL for the web page on which the player was embedded, a Windows Media metafile, or “-“if the player does not take advantage of either of the above options.

cs(User-Agent)

User Agent (Client)

The user agent used to play the stream. Typically, this field is set to the value used to report the User-Agent HTTP protocol header.

cs-media-name

Filename (Media)

The filename of the content that was streamed.

cs-media-role

Playlist Role

The role of the server-side playlist entry.

c-starttime

Start Time

The time offset, in seconds, from which the content was uploaded to the edge server. For live streaming, this field is set to zero.

c-status

Status (Client)

The client’s HTTP status code.

cs-uri-stem

Request URL

The URL to the stream path. This URL does not include the stream name.

cs-url

Request URL

The URL requested by the client.

cs-user-name

User Name

This field always reports “-.”

c-totalbuffertime

Buffering Time (Client)

The total amount of time, in seconds, that the client underwent buffering.

date

Event Date

The date when the event took place. The format for this field is YYYY-MM-DD (e.g., 2012-03-01).

·       YYYY: Indicates a year in the Gregorian calendar using a four digit number (e.g., 2012).

·       MM: Indicates a month of the year between 01 (January) and 12 (December).

·       DD: Indicates a day of the month between 01 and 31.

filelength

File Length

The length, in seconds, of the ASF file. Typically, the ASF file is the WMV or WMA that you are streaming. For live streaming, this field is set to zero.

filesize

File Size

The size, in bytes, of the ASF file. Typically, the ASF file is the WMV or WMA that you are streaming. For live streaming, this field is set to zero.

protocol

Protocol

The protocol used to stream content to the client. Valid values for this field are: http, rtsp, or asfm.

sc-bytes

Bytes

The number of bytes received by the client.

s-content-path

Content Path

The URL to the content streamed to the client. This is the URL rewritten by our edge servers.

s-cpu-util

CPU Utilization (Edge Server)

The CPU load on the edge server.

s-dns

Hostname (Client)

The hostname of the edge server that streamed the content to the client.

s-ip

IP Address (Client)

The IP address of the edge server that streamed the content to the client.

s-pkts-sent

Sent Packets

The number of ASF data packets sent by the server.

s-proxied

Server Proxy

Indicates whether the log was forwarded by a proxy. This field should be set to zero.

s-session-id

Session ID

The ID for the server session that streamed your content.

s-totalclients

Total Clients

The number of clients connected to the edge server.

time

Event Time

Identifies the time of the event. The format for this field is hh:mm:ss (e.g., 20:00:00).

·       hh: Indicates an hour of the day (GMT) between 00 and 24.

·       mm: Indicates minutes between 00 and 59.

·       ss: Indicates seconds between 00 and 59.

transport

Transport Protocol

The transport protocol used to stream content to the client. Valid values for this field are: TCP and UDP.

videocodec

Video Codec

The video codec used by the client to decode the video stream.

x-duration

Event Duration

The number of seconds that the stream has played.

Third-Party Log Analysis Tools

Log data is collected from multiple servers around the world and then combined into a single log file. As a result of dealing with servers from the around the world, the time stamps associated with each logged item may not appear in sequential order. This may cause an issue with certain third-party log analysis tools. Therefore, you may need to adjust the configuration of your log analysis tool. Please refer to the documentation of your log analysis tool for configuration instructions.

Note: Certain log data, such as the loading of content into RAM or the pre-caching of content, is generated from communication between our servers. The URL for these log records will be recorded as http://localhost/ or http://127.0.0.1/. You will need to configure your log analysis tool to exclude or ignore these entries.

Note: Although logged data may not appear in sequential order in the log files, the timestamp for each logged item will accurately reflect when the action took place using the GMT time zone.

Appendix A

Cache Status Codes

Each cache status that is reported for CDN activity is defined below.

Cache Status

Description

CONFIG_NOCACHE

This status indicates that a customer-specific configuration on our edge servers prevented the asset from being cached. For example, an HTTP Rules Engine rule can prevent an asset from being cached by enabling the Bypass Cache feature for qualifying requests.

NONE

This status indicates that a cache content freshness check was not performed. This check is skipped when Token-Based Authentication denies a request or when an HTTP request method is used that bypasses cache (e.g., PUT, DELETE, etc).

TCP_CLIENT_REFRESH_MISS

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.

By default, our servers prevent an HTTP client from forcing our edge servers to retrieve a new version of the asset from the origin server. However, this behavior can be overridden through the use of the HTTP Rules Engine feature called “Honor No-Cache Request.”

TCP_EXPIRED_HIT

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. An expired request typically results in a revalidation request to the origin server. In order for a TCP_EXPIRED_HIT to occur, the origin server must indicate that a newer version of the asset does not exist. This type of situation will typically update that asset’s Cache-Control and Expires headers.

TCP_EXPIRED_MISS

This status is reported when a newer version of an expired cached asset is served from the POP to the client. This occurs when the TTL for a cached asset has expired (e.g., expired max-age) and the origin server returns a newer version of that asset. This new version of the asset will be served to the client instead of the cached version. Additionally, it will be cached on the edge server and the client.

TCP_HIT

This status is reported when a request is served directly from the POP to the client. An asset is immediately served from a POP when it is cached on the POP closest to the client and it has a valid TTL. TTL is determined by the Cache-Control: s-maxage, Cache-Control: max-age, and Expires headers.

TCP_MISS

This status indicates that a cached version of the requested asset was not found on the POP closest to the client. The asset will be requested from either an origin server or an origin shield server. If the origin server or the origin shield server returns an asset, it will be served to the client and cached on both the client and the edge server. Otherwise, a non-200 status code (e.g., 403 Forbidden, 404 Not Found, etc.) will be returned.

UNCACHEABLE

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. These types of requests are served from the origin server.

Appendix B

Privileges

This section defines the privileges that can be assigned to a user. These privileges are listed in the order in which they appear on the Add/Edit User page.

Indentation is used to indicate parent/child relationships. In the following example, we can tell that the child and the grandchild privilege both pertain to the parent privilege.

Parent Privilege

               Child Privilege

                              Grandchild Privilege

Reminder: Keep in mind that granting a child privilege in the MCC will automatically grant the parent privilege.

Certain privileges only determine whether a tab/menu will be enabled. If you grant this type of privilege to a user, then the tab and the corresponding fly-out menu item will enabled for that user. If the user navigates to that tab or fly-out menu item, then the first child page, as determined by the order in which the permissions are listed below, for which that user has been granted access will be loaded. If all of the children of that parent privilege have been denied to that user, then the user will receive a message indicating that he does not have sufficient access.

Privilege

Secures

Additional Information

Home

MCC home page
(Home tab)

If a user does not have this privilege, then the default start page for that user will be the page associated with the first tab for which that user has privileges. This is calculated from the left hand side of the page to the right.

Media Manager

Media Manager tab

 

File Management

File Management page (Media Manager tab)

 

FTP

FTP page
(Media Manager tab)

This privilege also determines whether a user will be able to authenticate to CDN storage via a third-party FTP client.

HTTP Large

HTTP Large tab

 

HTTP Large Object

HTTP Large Object page (HTTP Large tab)

This privilege does not affect a user’s ability to use the URLs that are displayed on this page.

Customer Origin

Customer Origin page
(HTTP Large tab)

 

My Edge

My Edge page
(HTTP Large tab)

 

Token Auth

Token Auth page
(HTTP Large tab)

This privilege does not control whether a knowledgeable user with the proper resources (i.e., current encryption key and encoder/decoder) can encrypt and/or decrypt token values.

Country Filtering

Country Filtering page
(HTTP Large tab)

 

Edge Cnames

Edge Cnames page
 ( HTTP Large tab)

 

Cache Settings

Cache Settings sub navigation tab
(HTTP Large tab)

 

Query-String Caching

Query-String Caching page
(HTTP Large tab)

 

Query-String Logging

Query-String Logging page
(HTTP Large tab)

 

Compression

Compression page
(HTTP Large tab)

 

HTTP Streaming

HTTP Streaming sub navigation tab
(HTTP Large tab)

This privilege or its sub privileges do not affect a user’s ability to use Smooth Streaming URLs.

Live Smooth Streaming

Live Smooth Streaming page
(HTTP Large tab)

 

On-Demand HLS &HDS

On-Demand HLS &HDS page
(HTTP Large tab)

 

On-Demand Smooth Streaming

On-Demand Smooth Streaming page
(HTTP Large tab)

 

Resources

Resources page
(HTTP Large tab)

 

Rules Engine

Rules Engine page
(HTTP Large tab)

 

HTTP Small

HTTP Small tab

 

HTTP Small Object

HTTP Small Object page
(HTTP Small tab)

This privilege does not affect a user’s ability to use the URLs that are displayed on this page.

Customer Origin

Customer Origin page
(HTTP Small tab)

 

My Edge

My Edge page
(HTTP Small tab)

 

Token Auth

Token Auth page
(HTTP Small tab)

This privilege does not control whether a knowledgeable user with the proper resources (i.e., current encryption key and encoder/decoder) can encrypt and/or decrypt token values.

Country Filtering

Country Filtering page
(HTTP Small tab)

 

Edge Cnames

Edge Cnames page
(HTTP Small tab)

 

Cache Settings

Cache Setting sub
navigation tab
(HTTP Small tab)

 

Query-String Caching

Query-String Caching page
(HTTP Small tab)

 

Query-String Logging

Query-String Logging page
(HTTP Small tab)

 

Compression

Compression page
(HTTP Small tab)

 

Rules Engine

Rules Engine page
(HTTP Small tab)

 

ADN

ADN tab

 

Application Delivery Network

Application Delivery Network page
(ADN tab)

This privilege does not affect a user’s ability to use the URLs that are displayed on this page.

Customer Origin 

Customer Origin page
(ADN tab)

 

My Edge

My Edge page
(ADN tab)

 

Token Auth

Token Auth page
(ADN tab)

This privilege does not control whether a knowledgeable user with the proper resources (i.e., current encryption key and encoder/decoder) can encrypt and/or decrypt token values.

Country Filtering

Country Filtering page
(ADN tab)

 

Edge Cnames

Edge Cnames page
(ADN tab)

 

Edge Optimizer

Edge Optimizer sub navigation tab
(ADN tab)

 

Overview

Overview page
(ADN tab)

 

Site Manager

Site Manager page
(ADN tab)

 

Template Manager

Template Manager page
(ADN tab)

 

Meta Data Flush

Meta Data Flush page
(ADN tab)

 

Cache Settings

Cache Setting sub
navigation tab
(ADN tab)

 

Query-String Caching

Query-String Caching page
(ADN tab)

 

Query-String Logging

Query-String Logging page
(ADN tab)

 

Compression

Compression page
(ADN tab)

 

Rules Engine

Rules Engine page
(ADN tab)

 

Windows

Windows tab

 

Windows Media Streaming

Windows Media Streaming page
(Windows tab)

This privilege does not affect a user’s ability to use the URLs that are displayed on this page.

My Edge

My Edge page
(Windows tab)

 

Publishing Points

Publishing Points page
(Windows tab)

 

Token Auth

Token Auth page
(Windows tab)

This privilege does not control whether a knowledgeable user with the proper resources (i.e., current encryption key and encoder/decoder) can encrypt and/or decrypt token values.

Flash

Flash tab

 

Flash Streaming

Flash Streaming page
(Flash tab)

This privilege does not affect a user’s ability to use the URLs that are displayed on this page.

Customer Origin

Customer Origin page
(Flash tab)

 

My Edge

My Edge page
(Flash tab)

 

Token Auth

Token Auth page
(Flash tab)

This privilege does not control whether a knowledgeable user with the proper resources (i.e., current encryption key and encoder/decoder) can encrypt and/or decrypt token values.

Live Auth

Live Auth page
(Flash tab)

 

Edge Cnames

Edge Cnames page
(Flash tab)

 

FMS Labs

FMS Labs page
(Flash tab)

 

Advanced Settings

Advanced Settings sub navigation tab
(Flash tab)

 

SWF Verification

SWF Verification page
(Flash tab)

 

Server Side Archiving

Server Side Archiving page
(Flash tab)

 

Protocol Restriction

Protocol Restriction page
(Flash tab)

 

Reports

Reports tab

 

Core Reports

Core Reports sub
navigation tab
(Reports tab)

 

Traffic Summary

Traffic Summary page
(Reports tab)

 

Bandwidth

Bandwidth side
navigation tab
(Reports tab)

Each individual Bandwidth report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        HTTP Large

·        HTTPS Large

·        HTTP Small

·        HTTPS Small

·        Windows

·        Flash

·        ADN

·        ADN SSL

Data Transferred

Data Transferred side navigation tab
(Reports tab)

Each individual Data Transferred report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        HTTP Large

·        HTTPS Large

·        HTTP Small

·        HTTPS Small

·        Windows

·        Flash

·        ADN

·        ADN SSL

Hits

Hits side navigation tab
(Reports tab)

Each individual Hits report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        All Platforms

·        HTTP Large

·        HTTP Small

·        Windows

·        Flash

·        ADN

Cache Statuses

Cache Statuses side navigation tab
(Reports tab)

Each individual Cache Statuses report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        All Platforms

·        HTTP Large

·        HTTP Small

·        ADN

Cache Hit Ratio

Cache Hit Ratio side navigation tab
(Reports tab)

Each individual Cache Hit Ratio report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        All Platforms

·        HTTP Large

·        HTTP Small

·        ADN

Cnames

Cnames side navigation tab
(Reports tab)

Each individual Cnames report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        All Platforms

·        HTTP Large

·        HTTP Small

·        Flash

·        ADN

CDN Storage

CDN Storage side
navigation tab
(Reports tab)

 

Usage

Usage page
(Reports tab)

 

IPv4/IPv6

IPv4/IPv6 side navigation tab
(Reports tab)

 

Data Transferred

Data Transferred page
(Reports tab)

 

Notes

Notes page
(Reports tab – Core Reports sub navigation tab)

 

Custom Reports

Custom Reports sub navigation tab
(Reports tab)

 

Report Codes

Report Codes page
(Reports tab)

Each individual Report Codes report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        All Platforms

·        HTTP Large

·        HTTP Small

·        Flash

·        ADN

Notes

Notes page
(Reports tab – Custom Reports sub navigation tab)

 

Advanced HTTP Reports

Advanced HTTP Reports sub navigation tab
(Reports tab)

 

HTTP Large Platform

HTTP LargePlatform side navigation tab
(Reports tab)

Each individual Advanced HTTP (HTTP Large) report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        World Map

·        United States Map

·        Canada Map

·        Europe Map

·        Asia Pacific Map

·        Top Cities

·        Top Countries

·        Daily Summary

·        By Hour

·        By File

·        By File Detail

·        By File Type

·        By Directory

·        By Browser

·        By Referrer

·        By Download

·        By 404 Errors

Notes

Notes page
(Reports tab – Advanced HTTP Reports sub navigation tab)

 

Advanced ADN Reports

Advanced ADN Reports sub navigation tab
(Reports tab)

 

ADN Platform

ADN Platform side
navigation tab
(Reports tab)

Each individual Advanced ADN report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        World Map

·        United States Map

·        Canada Map

·        Europe Map

·        Asia Pacific Map

·        Top Cities

·        Top Countries

·        Daily Summary

·        By Hour

·        By File

·        By File Detail

·        By File Type

·        By Directory

·        By Browser

·        By Referrer

·        By Download

·        By 404 Errors

Notes

Notes page
(Reports tab – Advanced ADN Reports sub navigation tab)

 

Advanced Streaming Reports

Advanced Streaming Reports sub navigation tab
(Reports tab)

 

Flash Streaming

Flash Streaming side navigation tab
(Reports tab)

Each individual Flash Streaming report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        World Map

·        United States Map

·        Canada Map

·        Europe Map

·        Asia Pacific Map

·        Top Cities

·        Top Countries

·        Daily Summary

·        By Hour

·        By File

·        By File Detail

·        By Directory

·        By Referrer

Windows Streaming

Windows Streaming side navigation tab
(Reports tab)

Each individual Windows Streaming report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        World Map

·        United States Map

·        Canada Map

·        Europe Map

·        Asia Pacific Map

·        Top Cities

·        Top Countries

·        Daily Summary

·        By Hour

·        By File

·        By File Detail

·        By Directory

·        By Referrer

Notes

Notes page
(Reports tab – Advanced Streaming  Reports sub navigation tab)

 

Real-Time Stats

Real-Time Stats sub navigation tab
(Reports tab)

Each individual Real-Time Statistics report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        Overview

·        HTTP Large Object

·        HTTP Small Object

·        ADN

·        Windows Streaming

·        Flash Streaming

·        Other Stats

·        Real-Time Alerts

Edge Performance Analytics

Edge Performance Analytics sub navigation tab
(Reports tab)

 

Overview

Overview page
(Reports tab)

 

HTTP Large Object

HTTP Large Object page
(Reports tab)

Each individual HTTP Large (Edge Performance Analytics) report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        Daily Summary

·        Hourly Summary

·        Protocols

·        HTTP Methods

·        URLs

·        Cnames

·        Origins

·        Geo POPs

·        Clients

·        Cache Statuses

·        NONE Details

·        CONFIG_NOCACHE Details

·        UNCACHEABLE Details

·        TCP_HIT Details

·        TCP_MISS Details

·        TCP_EXPIRED_HIT Details

·        TCP_EXPIRED_MISS Details

·        TCP_CLIENT_REFRESH_MISS Details

·        Client Request Types

·        User Agents

·        Referrers

·        Compression Types

·        File Types

·        Unique Files

·        Token Auth Summary

·        Token Auth Deny Details

·        HTTP Response Codes

·        404 Errors

·        403 Errors

·        4xx Errors

·        504 Errors

·        502 Errors

·        5xx Errors

HTTP Small Object

HTTP Small Object page
(Reports tab)

Each individual HTTP Small Object (Edge Performance Analytics) report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        Daily Summary

·        Hourly Summary

·        Protocols

·        HTTP Methods

·        URLs

·        Cnames

·        Origins

·        Geo POPs

·        Clients

·        Cache Statuses

·        NONE Details

·        CONFIG_NOCACHE Details

·        UNCACHEABLE Details

·        TCP_HIT Details

·        TCP_MISS Details

·        TCP_EXPIRED_HIT Details

·        TCP_EXPIRED_MISS Details

·        TCP_CLIENT_REFRESH_MISS Details

·        Client Request Types

·        User Agents

·        Compression Types

·        File Types

·        Unique Files

·        Token Auth Summary

·        Token Auth Deny Details

·        HTTP Response Codes

·        404 Errors

·        403 Errors

·        4xx Errors

·        504 Errors

·        502 Errors

·        5xx Errors

Download Manager

Download Manager sub navigation tab
(Reports tab)

Each individual Download Manager report has a dedicated privilege that controls whether a user will be allowed to access the page on which that report resides. These privileges are listed below.

·        Download Summary

·        Download Package Detail

·        Package Download Status

·        Sequence Detail

Tools

Tools tab

 

Download Manager

Download Manager page
(Tools tab)

 

DLM Diagnostic Tool

DLM Diagnostic Tool sub navigation tab
(Tools tab)

Each individual Download Manager tool and resource page has a dedicated privilege that controls whether a user will be allowed to access it. These privileges are listed below.

·        Package Generator

·        Resources

·        EULA

Players

Players sub navigation tab
(Tools tab)

 

JW Player

JW Player page
(Tools tab)

 

Admin

Admin tab

 

Users

Users page
(Admin tab)

This privilege is required to modify a user’s custom ID.

Company Profile

Company Profile page
(Admin tab)

 

Company Settings

Company Settings sub navigation tab
(Admin tab)

 

Raw Log Settings

Raw Log Settings page
(Admin tab)

 

Rule Settings

Rule Settings page
(Admin tab)

 


Glossary

A

Asset

This term refers to a resource that contains header information and a body that can be served to clients. Examples of assets include files and dynamic content.

C

Cache

This term refers to the storage of data to improve data delivery performance. When used in reference to our CDN, it refers to the temporary storage of an asset on an edge server or an origin shield server. Cache increases the speed through which that particular edge server can deliver that asset for subsequent requests.

CDN

Our content delivery network (CDN) consists of points-of-presence (POPs) that are placed at critical network and geographical locations around the world. This allows us to place content at the edge of the Internet allowing for faster downloads by your end-users.

CDN Domain

This term refers to a domain name assigned to your account. In the following examples of CDN domains, xxxx represents your CDN account number.

·        Your_account_name_web.Gravlab.net [for website assets if this feature has been turned on]

·        your_account_name.gravlab.net

·        fms.xxxx.Gravlab.net

·        wms.xxxx.Gravlab.net

CDN Origin

This term refers to a storage server on our CDN. Our CDN origin servers are in close proximity to our POPs, in order to provide optimal conditions for transferring data from a CDN origin server to your end-users via our POPs.

CDN Origin Identifier

This type of identifier in the CDN URL indicates that requested asset should be retrieved from the CDN origin server. A CDN origin identifier is indicated by “00”as the starting two numbers in the CDN URL path.

CDN URL

This type of URL identifies a location or an asset on our content delivery network. The following diagram indicates the different components in a CDN URL. Keep in mind that xxxx represents your CDN account number.

CDN URL Path

This term refers to the portion of the CDN URL that appears after the CDN domain. It provides the relative path to a folder or an asset on either a CDN or customer origin server. In the following examples of CDN URL paths, xxxx represents your CDN account number.

·        /00xxxx

·        /00xxxx/Videos/2012/11/

·        /00xxxx/Videos/2012/11/Presentation01.flv

CDN/Edge CNAME URL Query

This term refers to the query string that appears after a question mark in a CDN or edge CNAME URL. If Token-Based Authentication is protecting the requested content, then a token value should appear directly after the question mark.

CNAME

A Canonical Name (CNAME) record is used to indicate that a domain name is an alias of another domain name. A CNAME record must be registered on a Domain Name System (DNS). This term should not be confused with edge CNAME.

Content Access Point

It provides a point of reference to any folder on a CDN or customer origin server. This relative path starts directly after the CDN domain. The proper syntax for a content access point is “/yyxxxx/path,”where yy stands for the identifier and xxxx stands for the CDN account number. The term path is optional and stands for the path to the folder specified by an edge CNAME configuration.

Customer Origin

This term refers to a storage server that is external to our CDN. Assets can be delivered from your storage server to your end-users via our POPs.

Customer Origin Identifier

This type of identifier in the CDN URL indicates that requested asset should be retrieved from the customer origin server. A customer origin identifier is indicated by “80”as the starting two numbers in the CDN URL path.

D

Domain Root

This term identifies the top and second-level domains associated with the CDN domain name.  An example of a domain root is “google.com.”

Dynamic Streaming

This technology, also known as Adaptive Streaming, allows a player (e.g., Silverlight) to dynamically switch between bit rate streams of varying quality levels, in order to provide an optimal viewing experience based on a client’s bandwidth and CPU usage. Smooth Streaming is an example of adaptive streaming.

E

Edge CNAME

This term refers to the mapping of a CNAME record to a directory on a CDN or customer origin server. The purpose of this mapping, which is only used by our CDN, is to establish a user-friendly alias for content served through the CDN. It relies upon your CNAME record being properly mapped on a DNS server.

Edge CNAME URL

This type of URL takes advantage of an edge CNAME to mask a CDN URL. This allows it to identify a location or an asset on our content delivery network using a more user-friendly URL. An edge CNAME URL is specific to the platform (i.e., HTTP Large, HTTP Small, or Flash Media Streaming) from which it was configured.

In the following examples, the domain assigned to the edge CNAME is “www.mydomain.com.”In the first example, the edge CNAME references the following CDN URL: “http://wpc.xxxx.gravlab.net/00xxxx.”  In the following two examples, the edge CNAME references the following CDN URL: “http://wpc.xxxx.Gravlab.net/00xxxx/Videos.”

Edge CNAME URL

Points To

http://www.MyDomain.com/

http://wpc.xxxx.gravlab.net/00xxxx/

http://www.MyDomain.com/2012/11/

http://wpc.xxxx.Gravlab.net/00xxxx/Videos/2012/11/

http://wpc.xxxx.Gravlab.net/00xxxx/Videos/2012/11/Presentation01.flv

Edge CNAME URL Path

This term refers to the portion of the edge CNAME URL that appears after the edge CNAME. It provides the relative path to a folder or an asset on a CDN or customer origin server. In the following examples of edge CNAME URL paths, the edge CNAME points to the following CDN URL: “http://wpc.xxxx.Gravlab.net/00xxxx/Videos.”

Edge CNAME URL Path

Actual Edge CNAME URL

/2012/11/

http://wpc.xxxx.Gravlab.net/00xxxx/Videos/2012/11/

/2012/11/Show01.flv

http://wpc.xxxx.Gravlab.net/00xxxx/Videos/2012/11/Show01.flv

Edge Protocol

This term refers to the protocol (e.g., HTTP, RTMP, and MMS) used in a CDN URL or an edge CNAME URL.

Edge Server

This type of server is located near the edge of the Internet where its close proximity to your end-users allows it to deliver data more quickly than normal Internet communications. Our edge servers are integral component of our POPs.

Encryption Key

Token-Based Authentication requires the use of an encryption key to encrypt and decrypt token values. There are two types of encryption keys, which are a primary and a backup key. Both of these keys can be used to encrypt and decrypt token values.

F

Flash Live StreamCast

Please see Live StreamCast.

Flash On-Demand

This term refers to the streaming of Flash media content stored on an origin server through our CDN. This type of streaming uses Real-Time Messaging Protocol (RTMP, RTMPE, RTMPT, or RTMPTE) to deliver video to your clients.

G

Global Key

This type of Live Authentication key can be used to authenticate all live Flash streams. Only a single global key can be specified.

H

HTTP Large

This platform consists of dedicated edge servers that retrieve, cache, and serve large assets to your clients. These servers have been optimized to cache assets. A typical asset for the HTTP Large platform is larger than 300 KB.

HTTP Progressive Download

This method of streaming video content is performed through the HTTP protocol. Progressive downloads are not as secure as other streaming methods, since the entire asset will be stored on your client’s computer. This allows your client to save and share your content with other users.

HTTP Small

This platform consists of dedicated edge servers that retrieve, cache, and serve smaller content to your clients. These servers have been optimized to index files. A typical asset for the HTTP Small platform is smaller than 300 KB.

I

Identifier

It identifies how a request will be routed through our CDN. Examples of identifiers are:

·       00: CDN origin identifier

·       80: Customer origin identifier

·       20: Flash Media Streaming (Live StreamCast)

Ingest

This term refers to the process of capturing and transforming video into a stream.

Ingest Server

This term refers to the type of server that is dedicated to the process of capturing and transforming video into a stream. This type of server will then broadcast that stream throughout our CDN.

L

Live Authentication Key

This type of key authenticates a stream on the Flash Media Streaming platform before it is ingested by our publishing server. There are two types of live authentication keys, which are global and stream keys. When configuring your encoder, you must specify the stream name, a token delimiter, and then a global or stream key. The token delimiter that you should use depends on whether you are using Live Streaming or Live StreamCast.

·        Notation for Live StreamCast: < StreamName>?< LiveAuthenticationKey>

·        Notation for Live Streaming:  < StreamName>/< LiveAuthenticationKey>

Live Ingestion Point

This term refers to the location on a server where our CDN can access encoded media. There are two types of live ingestion points, which are pull source and publishing point.

Live StreamCast

This term refers to the streaming of a live Flash media stream through our CDN. This type of streaming uses Real-Time Messaging Protocol (RTMP, RTMPE, RTMPT, or RTMPTE) to deliver video to your clients.

Live Streaming Identifier

This type of identifier in the CDN URL indicates that requested asset should be streamed from the live ingestion point. A live stream identifier is indicated by “20”as the starting two numbers in the CDN URL path.

Load

This feature allows you to cache an asset on all of our POPs. This feature is unsupported for use with Windows Media Streaming platform or Live StreamCast (Flash Media Streaming).

M

Media Control Center (MCC)

This web application is provided to help you manage all of your CDN needs. The major features that are available from the MCC are CDN configuration settings, cache management, file management, reports, and analytics. Additionally, the MCC allows you to configure your organization’s settings, such as granting or denying access to the MCC. You can access the MCC through the following URL:

https://my.gravitylab.com

O

Origin Path

It references a relative path to a folder or an asset in a CDN URL. This type of path follows the content access point.

Origin Server

This term refers to the servers that store the assets that will be distributed by our POPs. There are two types of origin servers, which are CDN origin and customer origin servers.

Origin Shield

This feature provides a layer of protection for your customer origin server by creating an intermediate caching layer between it and our edge servers. This caching layer resides on one or more of our point-of-presence (POPs). Requests that have not been previously cached on a POP will be channeled through the closest origin shield server. The origin shield server will then either serve a cached version of the requested content or retrieve it from your customer origin server. This feature reduces the amount of bandwidth used on your customer origin server, since most requests will be handled by the origin shield server.

P

Player URL

A media player uses this type of URL to stream content. It identifies the location of the streamer on the live ingestion point.

Point-of-Presence (POP)

A point-of-presence, or data center, is an access point to the Internet. The main components of a POP are edge servers, CDN origin servers, and publishing servers.

Pre-Cached

A pre-cached asset means that it has been loaded to all of our POPs. Pre-caching your assets allows even quicker content delivery to your clients, since it ensures that the requested asset will not have to be retrieved from the origin server.

Publishing Point

This term refers to the location on the publishing server to which your encoder will broadcast encoded media.

Publishing Server

This term refers to a CDN server that will redistribute encoded media as a streamer that will be broadcast to your end-users via our POPs.

Pull Source

This term refers to the location on an external server from which a broadcasted stream will be retrieved by our publishing server.

Pull Stream

This type of stream requires that our servers retrieve, or pull, a live stream from a server with a public IP address.

Purge

This feature allows you to remove the cached version of an asset from all of our edge servers and origin shield servers. A purge can be performed on a folder or an individual asset.

Push Stream

This type of stream requires your encoder to send, or push, encoded video to a CDN server. From there, our server will create a stream and deliver it to clients that request it.

Q

Query String

Additional data can be appended to a URL (e.g., http://www.server.com/index.html?Data=xyz). This information can be used in a variety of ways. Our CDN allows you to leverage this information to determine how content will be cached. Additionally, you can choose to store query string information in our log files. Keep in mind that query string caching is not supported on the Flash Media Streaming or the Windows Media Streaming platforms.

R

Request

A request consists of a set of headers and a body sent from a client. This header data and the body define the requested content. Typically, a request is sent from a client to an edge server. If the requested content is not found, then our edge servers will forward this request to an origin server.

Response

A response consists of the headers and the body sent from a server responding to a request. If an origin server is returning a response, then this response will be sent to an edge server. The edge server will then forward the response to a client.

S

Server Side Archiving

This feature allows you to archive live Flash streams on an origin server. This allows you to provide video on-demand capabilities to live Flash streams.

Stream

A stream consists of the delivery of audio/video content in a format that allows your clients to play it back through a multimedia player.

Stream Key

This type of Live Authentication key can only authenticate a Flash stream when it is published to the path associated with it.

T

Time to Live (TTL)

This term refers to the amount of time that a cached asset is still considered fresh. Our edge servers will continue to serve a cached version of an asset while its TTL has not expired. An asset’s TTL is calculated by the Cache-Control and Expires headers associated with the response sent by a CDN or customer origin server.

Token

A token or a token value must be provided when a client requests content protected with Token-Based Authentication. Each token value contains security requirements that have been encoded using an encryption key. A token value can be specified by appending a question mark and the token value to the CDN URL path.

Token-Based Authentication

It requires a token value to be supplied when a user requests an asset from a protected folder. This token value is then decrypted on our server. If the user meets the specified requirement(s), then the asset will be delivered. Otherwise, the user will be denied access to the asset.

W

Windows Media Live Streaming

This term refers to the streaming of a live Windows media stream through our CDN. Although this type of streaming can use MMS as the protocol identifier, it will actually use either the HTTP or RTSP protocol to deliver your video to your clients.

Windows Media On-Demand Streaming

This term refers to the streaming of Windows media content stored on our CDN storage service. Although this type of streaming can use MMS as the protocol identifier, it will actually use either the HTTP or RTSP protocol to deliver your video to your clients.

0