Akamai mPulse

Overview

Connect Datadog with Akamai mPulse to collect real user monitoring (RUM) metrics and gain visibility into how end users perceive performance of a website. Gain comprehensive visibility across your web stack by analyzing and correlating RUM metrics alongside performance data from your CDN and backend infrastructure.

Use Datadog’s out-of-the-box dashboard and monitors to:

Get an overview of key metrics like bounce rate, user sessions and page load times
Investigate the source of user facing slowdown, whether frontend or backend
Monitor page load times and page groups

Correlate metrics with real-time data from Akamai DataStream 2, NGINX, MYSQL, and more than 600 other technologies for a frontend to backend view of your webstack.

Setup

Installation

Install the integration with the Datadog Akamai mPulse integration tile.

Configuration

An apiKey and apiToken are required to configure the Akamai mPulse integration.

Generate an API key

The apiKey is an auto-generated value that uniquely identifies your site’s data (beacons) found in your mPulse portal.

The "Apps" menu option and `apiKey` attribute are only visible to App Administrators.

Find your apiKey by navigating to the “Central” page
Click Apps on the left panel. ,
Select the app name you want to monitor to open a configuration page that contains your apiKey.

Generate an API token

See the Akamai documentation for API token then:

Log into mpulse.soasta.com.
Go to My Settings on the leftmost panel.
Click “Generate” in the API token area.

Data Collected

Metrics


akamai.mpulse.bouncerate (gauge)	The percentage of visitors who enter the site and then leave Shown as percent
akamai.mpulse.clientroundtriptime.p50 (gauge)	The 50th percentile of the round-trip time between the browser and the Akamai edge server (nearest to the end user) Shown as millisecond
akamai.mpulse.clientroundtriptime.p95 (gauge)	The 95th percentile of the round-trip time between the browser and the Akamai edge server (nearest to the end user) Shown as millisecond
akamai.mpulse.dns.p50 (gauge)	The 50th percentile of DNS resolution time Shown as millisecond
akamai.mpulse.dns.p95 (gauge)	The 95th percentile of DNS resolution time Shown as millisecond
akamai.mpulse.domload.p50 (gauge)	The 50th percentile of domLoading - navigationStart Shown as millisecond
akamai.mpulse.domload.p95 (gauge)	The 95th percentile of domLoading - navigationStart Shown as millisecond
akamai.mpulse.domready.p50 (gauge)	The 50th percentile of domComplete - navigationStart Shown as millisecond
akamai.mpulse.domready.p95 (gauge)	The 95th percentile of domComplete - navigationStart Shown as millisecond
akamai.mpulse.firstbyte.p50 (gauge)	The 50th percentile of the time from navigation start to first byte Shown as millisecond
akamai.mpulse.firstbyte.p95 (gauge)	The 95th percentile of the time from navigation start to first byte Shown as millisecond
akamai.mpulse.firstcontentfulpaint.p50 (gauge)	The 50th percentile of the time when the browser displays content for the first time Shown as millisecond
akamai.mpulse.firstcontentfulpaint.p95 (gauge)	The 95th percentile of the time when the browser displays content for the first time Shown as millisecond
akamai.mpulse.firstinputdelay.p50 (gauge)	The 50th percentile of how quickly the page was able to respond to the user’s first interaction Shown as millisecond
akamai.mpulse.firstinputdelay.p95 (gauge)	The 95th percentile of how quickly the page was able to respond to the user’s first interaction Shown as millisecond
akamai.mpulse.firstlastbyte.p50 (gauge)	The 50th percentile of the time from first byte to onload (or whenever the page is considered ready) Shown as millisecond
akamai.mpulse.firstlastbyte.p95 (gauge)	The 95th percentile of the time from first byte to onload (or whenever the page is considered ready) Shown as millisecond
akamai.mpulse.firstpaint.p50 (gauge)	The 50th percentile of the time when the browser first rendered after navigation Shown as millisecond
akamai.mpulse.firstpaint.p95 (gauge)	The 95th percentile of the time when the browser first rendered after navigation. Shown as millisecond
akamai.mpulse.longtaskstime.p50 (gauge)	The 50th percentile of the sum of the amount of time of LongTasks, which are browser tasks that take over 50 ms Shown as millisecond
akamai.mpulse.longtaskstime.p95 (gauge)	The 95th percentile of the sum of the amount of time of LongTasks, which are browser tasks that take over 50 ms Shown as millisecond
akamai.mpulse.pageload.p50 (gauge)	The 50th percentile of page load time Shown as millisecond
akamai.mpulse.pageload.p95 (gauge)	The 95th percentile of page load time Shown as millisecond
akamai.mpulse.pageviews (count)	Number of page views Shown as view
akamai.mpulse.sessions (count)	Number of user sessions Shown as session
akamai.mpulse.ssl.p50 (gauge)	The 50th percentile of SSL handshake time Shown as millisecond
akamai.mpulse.ssl.p95 (gauge)	The 95th percentile of SSL handshake time Shown as millisecond
akamai.mpulse.tcp.p50 (gauge)	The 50th percentile of TCP connect time Shown as millisecond
akamai.mpulse.tcp.p95 (gauge)	The 95th percentile of TCP connect time Shown as millisecond
akamai.mpulse.timetofirstinteraction.p50 (gauge)	The 50th percentile of the time when the user first tries to interact with the page Shown as millisecond
akamai.mpulse.timetofirstinteraction.p95 (gauge)	The 95th percentile of the time when the user first tries to interact with the page Shown as millisecond
akamai.mpulse.timetointeractive.p50 (gauge)	The 50th percentile of the time the user interacts with the page Shown as millisecond
akamai.mpulse.timetointeractive.p95 (gauge)	The 95th percentile of the time the user interacts with the page Shown as millisecond
akamai.mpulse.timetovisuallyready.p50 (gauge)	The 50th percentile of the time when the page view is ready to use Shown as millisecond
akamai.mpulse.timetovisuallyready.p95 (gauge)	The 95th percentile of the time when the page view is ready to use Shown as millisecond