AMP - Debugging / Troubleshooting

Document created by Herberth Alvarado Employee on Mar 23, 2016Last modified by Herberth Alvarado Employee on Apr 14, 2017
Version 27Show Document
  • View in full screen mode

Maintainer: Maverick Chacon Garro

This document is part of Adaptive Media Player Web User Guide

Please use the non-minified versions of the amp JS files to aid troubleshooting. Add amp-debug=true to URL query string in order to invoke the debug player and see loglines in the console

 

 

 

AMP Logs

 

To activate the AMP logs use the query string parameter "amp-debug=true", this is the basic way to find issues, or to report them. So it is important to know it exist.

 

Flash Debugging


You can have you own good Flash debugging setup.

STEP 1:

In Firefox, Safari: (and you can let Chrome do its own thing, which has its own Flash player).

Be sure to have Flash debugger

https://www.adobe.com/support/flashplayer/debug_downloads.html

In a Flash right-click menu, you’ll see the word “Debugger”

 



When you have this, then on Firefox and Safari,  you will have

A) Popups with error info when a Flash run-time error is encountered (usually)

B) ability to run debugger tool like Vizzy below

 

STEP 2:

Have Vizzy installed, so you can look at “Flash console"

https://code.google.com/p/flash-tracer/downloads/detail?name=Vizzy-mac-3.91.zip

 

Links of interest:

Article listing different testing players

Complete list of support players that Akamai provides for testing purposes

 

Flash logs

You can enable flash logs in console by adding the following query string "amp-flash-log" in the player url. i.e

yourplayerdomain.com/home.html?amp-debug=true&amp-flash-log=true

 

 

Checking media source

In order to check current sources you can extract the instance player from the webpage by doing the following in the console log
var amp = document.getElementById('akamai-media-player').amp

and them using our API in order to get the source i.e

amp.getSrc() or amp.getSource()

 

For more info please read our API documentation AMP - API

 

Test AMP

If you want to test a specific and clean AMP version in order to discard any implementation issue or disrupt config you can do it using the following tool.

AMP-Builder

 

Steps for debug here on Desktop and Mobile

  1. Open the amp-builder
  2. Choose the right version (latest is selected by default).
  3. Enable the right media source according to your needs, or paste a specific source into the text fields.
  4. Check inline console (optional).
  5. Click on create button.


Any question about this tool please contact to Maverick Chacon

 

 

Media Analytics

Akamai beacons. There are two ways you can verify if the beacons are triggered as follow:

  1. In the browser Network tab filtering by “9.gif”
  2. Using the Integration Diagnoser.

 

Integration Diagnoser

 

Launch it in DEBUG mode by passing “AkamaiAnalytics_debug=1” as query string to the page. When the player is launched using the DEBUG mode, a pop-up window “Plug-in Integration Diagnoser” opens as shown below (pop-ups must be enabled in the browser).

 

The Plug-in Integration Diagnoser window helps you debug as follows:

  • Integration Errors, Warnings & Integration-related messages are shown in the window to help you verify the Integration.
  • Select the “BEACON” check box in the window to ensure that the plug-in makes proper beacon requests as the video starts playing. Here are the beacons that must be sent:
    • I-Beacon: A GET request starting with “?a=I” in query string. Should be sent when initiated.
    • S-Beacon: A GET request starting with “?a=S” in query string. Should be sent when play starts.
    • P-Beacon: Multiple GET requests starting with “?a=P” in query string. (Every 5 Minutes). Should be sent as the play progresses.
    • C-Beacon: A GET request starting with “?a=C” in query string. Should be sent when the playback completes.
    • E-Beacon: A GET request starting with “?a=E” in query string. This should be sent only if there is an error in playback (Either before play begins or during the play).
  • If you are unable to view the correct sequence of beacons being sent out, or are seeing ERROR messages that you are unable to solve (marked in red in the window), click “Send Results To Akamai” on the window to view information on sending debug information to Akamai Customer Care.

 

Streamsense Tags:

In the browser console filtering by "p?". In iPhone filtering by "p2?"

 

Comscore Tags:

In the browser console filtering by "b?".

 

Omniture beacons:

In the browser console filtering by the server name.

 

 

 

This document is part of Adaptive Media Player Web User Guide

Attachments

    Outcomes