Use this section to configure settings for monitoring and reporting. These tools provide visibility into your traffic patterns and audience behavior.

Content Provider Code

Required

Assign a unique Akamai Content Provider (CP) code to track reporting and billing data for traffic delivered through this Ion configuration.

Select an existing CP code

Your account team typically provides at least one CP code during provisioning. You can select the Content Provider Code from the list.

You can also assign an existing CP code to aggregate data from multiple configurations. Review these considerations before reusing a code:

• Granularity. Billing and reporting merge when configurations share a CP code. To maintain distinct data for this Ion configuration, use a new CP code.
• Log Delivery Service (LDS). If you plan to enable LDS, the selected CP code cannot be active on another configuration in the production network. It can, however, be shared with configurations on the staging network.

Create a new CP code

1. Click the Create new button and optionally provide a custom name.
2. Click Submit. The new CP code appears in the field with a unique numeric ID.

Use this ID to:

• Filter reports. View specific traffic data via the Traffic Reports tool in Akamai Control Center.
• Enable LDS. Attach Log Delivery Service support to this specific traffic stream.

To learn more, see Content Provider Code.

EdgeScape Template

This feature identifies a user's location, network, and connection speed. Akamai sends this data to your origin in the X-Akamai-Edgescape request header, allowing you to serve localized content.

📘

If your origin caches content based on these header values, consult your Akamai team to ensure your caching configuration is optimized for Geolocation.

To learn more, see Content Targeting (EdgeScape).

Log Request Details

The Akamai Log Delivery Service (LDS) aggregates logs from edge servers and delivers them to you on a custom schedule.

Set the options

Specify the data you wish to include in your logs:

• Log Host/Referer/User-Agent/Accept-Language Header. Standard HTTP headers for identifying request targets and client environments. Only Host is enabled by default.
• Cookie Mode. Choose to log all, none, or specific cookies. For example, sessionid.
• Include Custom Log Field. If enabled, you can manually define a specific header or variable to capture.
• Log Akamai Edge Server IP Address. Log the IP address of the ​Akamai​ edge server which served the response to the client.
• Log X-Forwarded-For Header. Log the X-Forwarded-For request header, if passed.

Add Log Delivery

After configuring the settings here, you need to activate the service in the Log Delivery application before going to production:

1. In Akamai Control Center, navigate to Analytics & monitor > Log Delivery.
2. Filter by your CP code.
3. Select Action > Start a log delivery > New.
4. Follow the wizard to finalize the delivery destination and format.

🚧

LDS takes 24-48 hours to activate. Configure this well before your production launch, as logs can't be collected retroactively.

To learn more, see Log Request Details.

Enhanced Debug

Enhanced Debug is a default, secure, and feature-rich method for diagnosing requests that replaces older Pragma debugging. It uses a time-limited authentication token generated from a customer-defined secret key to prevent unauthorized access.

Default setup

• Debugging Enabled. Enabled by default.
• Debug Key. The debug key validates the debugging auth token when ​Akamai​ processes the request. You also use this debug key to generate the auth token. The debug key value needs to be a 64-byte hex string. As a best practice, you can reuse the same debug key in your other configurations.
  To auto-generate a valid random string, click the refresh button.
• Disable Pragma Debugging. Disabled by default, meaning that the legacy debugging with the Pragma request header is no longer available. You should only enable Pragma debugging during a transition period, until you have updated all your systems to use Enhanced Debug.
• Global Request Number. By default, this returns the Global Request Number (GRN) in the Akamai-GRN response header for all requests, even if the request is not being debugged. For example: Akamai-GRN: 0.25313217.1562625611.27bb4bb. If you want to return a GRN for all requests, remove any instances of the Global Request Number behavior from your configuration.

To learn more, see Enhanced Debug.