Akamai DataStream2 (DS2) Logs

Bring Akamai CDN/WAF logs into APIContext so you can view external signal (e.g., TTFB) alongside internal delivery details (edge-to-origin timing, parent hops, etc.). This integration filters your DS2 stream to only include APIContext synthetic monitoring calls, minimizing volume and keeping your telemetry focused.

Who is this for?
APIContext Enterprise customers. If you also use Akamai TrafficPeak, we’ll coordinate directly with the TrafficPeak team to wire everything up.

What you’ll get

Consolidated Performance Metrics from external and internal sources, including DNS resolution, Connect Time, Time to First Byte (TTFB), Edge to Origin, Parent Hops, and other metrics available from DS2 data sets.

Prerequisites

Akamai Control Center access with permission to create DS2 stream definitions.
DataStream 2 enabled on your contract.
APIContext Enterprise plan.
(Optional) TrafficPeak subscription with your Akamai team.

Note on DS2 filtering
DS2 supports including/excluding log lines using match criteria (configured via the Log Request Details behavior). We’ll use this to isolate APIContext synthetic calls.

Before you start

Plan to create a new DS2 stream specifically for this integration (don’t modify an existing stream).
Identify the properties (Akamai configs) that your synthetic monitors hit.
Decide whether you’ll deliver logs to TrafficPeak (recommended if you already use it).

Step 1 — Let us know you're adding a DS2 integration

Email [email protected], or visit https://apicontext.com/support to open a ticket.
We will reply with confirmation of your plan, and a custom HTTPS endpoint to send the DS2 logs (if needed).

Step 2 — Create a new DS2 stream

Log in to Akamai Control Center → COMMON SERVICES → DataStream → Create stream.
Choose JSON log format.
For destination, select HTTPS endpoint and configure it with the custom endpoint provided by the APIContext support team.

For questions on DS2 configuration, please see DS2 documentation at: https://techdocs.akamai.com/datastream2/docs/features

Step 3 — Select data set fields (include TTFB)

In the Data sets step, include the following recommended fields:

Step 4 — Filter to APIContext synthetic traffic

Use DS2’s include/exclude match criteria (via the Log Request Details behavior) to only log synthetic calls that carry the APIContext header:

Header to filter on: X-APIContext-Agent
Action: Include log lines only when this header is present (or equals your expected value, if you set one).

This keeps the stream lightweight—volume tracks your synthetic cadence rather than full site traffic.

Why header (not UA)?
Headers are explicit and less fragile than user-agent parsing. DS2’s match criteria let you target request headers directly.

Step 5 — Add the APIContext `traceparent` to each log line

To correlate logs with synthetic journeys, add a custom log field that forwards the traceparent ID included with every APIContext synthetic request.

Name/value format in DS2: apic_traceparent=VALUE
Configure this using DS2’s Custom log field capability (defined in Log Request Details).

We’ll extract apic_traceparent into its own column on our end for joins and drill-downs.

Step 6 — Let us know!

Update your support request to let us know DataStream2 is configured.

If you have TrafficPeak, we will work with the TrafficPeak team directly to deliver our feed into your existing TrafficPeak account.

If you do not have TrafficPeak, we can add your DS2 logs into APIContext, using the custom HTTPS endpoint provided earlier.

Performance & volume notes

This integration is lightweight—it only logs filtered synthetic traffic based on your test cadence.