To use this feature you need to be part of an mPulse paid plan. For more information about setting up and using mPulse refer to the mPulse guide.
Before you begin, make sure that your property includes the mPulse behavior and that you have followed the set up instructions described in the mPulse guide.
Once the mPulse-enabled property is active on the Akamai production network, your data (beacons) are directed to your mPulse app. See How mPulse works to learn more.
Next, use the toggle button in the EdgeWorkers behavior to set Enable mPulse error reports to On.
To stop generating the EdgeWorkers error reports in mPulse you can set the toggle button to Off.
If mPulse is unavailable on your property you will be prompted to enable it before you can turn on the EdgeWorkers reports.
EdgeWorkers functions produce an HTTP 500 response if the event handler generates errors due to:
- Exceeding limits such as CPU and memory
- Log in to mPulse to enable and view the EdgeWorkers error reports.
- Select EdgeWorkers event handlers as an error source in the App Error List and App Error Summary dashboards.
Refer to the Explore mPulse system dashboards and widgets in the mPulse guide.
The mPulse error reports for EdgeWorkers include the following details.
|URL related to the beacon
Refer to the URLs section of the mPulse beacon description.
|Error message and stack trace
Refer to the Errors section of the mPulse beacon description.
Name of the EdgeWorker ID
|Includes fields from the User-Agent HTTP Request Header such as, browser family, major version, and device type.
|Refer to EdgeScape in the Akamai section of the mPulse beacon description.
|Edge Device Characteristics data
|Refer to EDC in the Akamai section of the mPulse beacon description.
|Includes the Property version, ARL ID, and CP Code.
Refer to Akamai info in the Akamai section.
|mPulse session ID
|Session ID generated by mPulse.
Refer to the Session section of the mPulse beacon description.
Updated 5 months ago