Sometimes the standard manual injection scenario is not appropriate for your installation. Use the following options to customize the process for your needs.
To set this up:
2. For each of your apps, add a line to the "start-time" script, shown in the red box below, to the header of each page right after the <head> tag, and any <meta> tags, before the entry that includes the location of the agent (adrum.js):
The app key for each of your apps is displayed in the relevant EUM configuration screen under Advanced->Customize your Deployment.
After you include the variable line, the start-time line and the agent, the <head> section in your EUM-monitored web pages should resemble the following example, although your app key will naturally be different for every app:
Previous versions of the agent can be found at
where VERSION is the version number (for example, 22.214.171.124) you want to access.
3. Add a line in the script, shown in the red box above, indicating your app key. The script must be in the header of the page directly after the <head> tag. This entry must be before the entry that includes the location of the agent (adrum.js). You must specify the app key if you are using the hosted script:
Your app key is displayed under Advanced->Customize your Deployment.
4. Optional: If you want to use a custom geo-server with the hosted version of the script, you also need to add a line defining the custom geo URL:
For more information on using a custom geo-server, see Use a Custom Geo Server For Web EUM.
5. Edit the path for adrum.js to point to the hosted location on Amazon:
After you include the app key, the start-time line, the custom geo-server URL (optional), and the agent URL, the <head> section in your EUM-monitored web page should resemble the following example, although your details will be somewhat different: