Software as a Service (SaaS)

Server Name Indication Readiness (SNI) report

For this report, a hostname is considered to be SNI capable if the client sends the server hostname in the Transport Layer Security (TLS) negotiation. If you want to create a certificate that uses SNI, you need to determine whether the hostnames that are covered under that certificate support SNI. The SNI Readiness report provides this information.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • CP code (required). Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.

Metrics

  • SSL connections. The total number of SSL connections for the selected CP code.

  • Non-SNI SSL connections by host. The total number of SSL connections by hostname that do not support SNI.

  • Non-SNI SSL connections by SaaS app/cust. For each hostname, the total number of SSL connections by SaaS application ID and SaaS customer ID that do not support SNI.

SaaS User Counts by Customer report

The SaaS User Counts by Customer report lets you view the total number of Software as a Service (SaaS) customers that traffic has been reported for, including the number of applications and users. You must identify a pattern for extracting customer ID and unique users using the SaaS Definitions Property Manager behavior.

Data granularity and retention
The SaaS User Counts report returns monthly data, for up to a period of three months. You must select the first of the month for the desired date range in the date picker, then select the period (one, two, or three months) in the filter panel. For example, if you would like to see data from May 1 to August 1, select May 1 in the date picker, then select 3 from the period filter options.

Filters

  • Contract (required). The contract that you want to see SaaS user counts.

  • Period (required). The number of months for which you want to see data, either 1, 2, or 3. Note that the report will always use the first of the month you selected as a start date.

  • Application ID. The ID for a SaaS application that you have configured for a specific contract using the SaaS Definitions Property Manager behavior. Limits results to a specific set of SaaS applications.

Metrics

  • Customer ID. Displays the ID whose pattern was defined using the SaaS Definitions Property Manager Behavior.

  • Total users. Displays the number of unique users accessing customer ID.

SaaS User Counts by application report

The Software as a Service (SaaS) User Counts by Application report lets you view the total number of users by SaaS application has reported traffic. You must identify a pattern for extracting application ID and unique users using the SaaS Definitions Property Manager behavior.

Data granularity and retention
SaaS User Counts is a report that returns monthly data, for up to three months. Select the first of the month for the desired date range in the date picker, then select the period (one, two, or three months) in the filter panel. For example, if you would like to see data from May 1 to August 1, select May 1 in the date picker, then select 3 from the period filter options.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • Contract (required). The contract containing SaaS user counts that you want to see.

  • Period (required). The number of months that you want to see data for, either 1, 2, or 3. Note that the report will always use the first of the month you selected as a start date.

Metrics

  • Application ID. Displays all SaaS applications and the total number of users accessing each application.

  • Total users. Displays the number of unique users accessing the application ID.

SaaS Traffic by Customer report

The Software as a Service (SaaS) Traffic by Customer report shows traffic data at a SaaS customer level.

Data granularity
This report shows daily data only.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • CP code (required). Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.

  • IP version (optional). The Internet Protocol (IP) version that traffic was generated from, either IPv4 or IPv6. If no IP version is selected, the report shows data for both IPv4 and IPv6.

  • Traffic type (optional). Either standard secure or non-secure. If no traffic type is chosen, the report shows data for both standard secure and non-secure.

  • Application ID (pending). The ID for a SaaS application that you have configured for a specific contract using the SaaS Definitions Property Manager Behavior. Limits results to a specific set of SaaS customers.

Metrics

  • Total edge bytes. Volume in bytes from the edge server to the end user.

  • Total edge hits. All hits with all response codes from the edge server to the end user.

  • Total midgress bytes. Volume in bytes delivered or served from ‚ÄčAkamai‚Äč Tiered Distribution network to edge servers.

  • Total midgress hits. All hits with all response codes delivered or served from ‚ÄčAkamai‚Äč Tiered Distribution network to edge servers.

SaaS Traffic by Application report

The Software as a Service (SaaS) Traffic by Application report provides traffic data at a SaaS application level.

Data granularity
This report shows daily data only.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • CP code (required). Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.

  • IP Version (optional). The Internet Protocol (IP) version from which traffic was generated, either IPv4 or IPv6. If no IP version is selected, the report shows data for both IPv4 and IPv6.

  • Traffic Type (optional). Either standard secure or non-secure. If no traffic type is chosen, the report shows data for both standard secure and non-secure.

  • Customer ID. The ID for a single SaaS-application-using customer that you have configured in your SaaS implementation. Limits results to a specific set of SaaS applications.

Metrics

  • Total edge bytes. Volume in bytes from the edge server to the end user.

  • Total edge hits. All hits with all response codes from the edge server to the end user.

  • Total midgress bytes. Volume in bytes delivered or served from ‚ÄčAkamai‚Äč Tiered Distribution network to edge servers.

  • Total midgress hits. All hits with all response codes delivered or served from ‚ÄčAkamai‚Äč Tiered Distribution network to edge servers.


Did this page help you?