Download PDF
Download page Browser End-User Monitoring.
Browser End-User Monitoring
On this page:
Prerequisites
- Set Up Browser RUM
- Obtain the App Key before enabling Browser instrumentation through JavaScript Agent injection
Configure Browser Instrumentation
You can customize browser Instrumentation from Instrumentation settings > Browser Instrumentation using SAP transaction code /DVD/APPD_CUST
.
The following table describes the fields and descriptions for Instrumentation Settings:
Field | Description |
---|---|
Hosting options | Determines where the JavaScript Agent files are to be hosted. See JavaScript Agent configuration.
|
Agent Version | It is provided when AppDynamics CDN hosting is selected. The default value is This field is hidden for hosting options other than AppDynamics CDN where the default value is |
Custom host | It is provided when Self-Hosting or Shared Hosting is selected. It is a mandatory field and the value should not contain prefixes like |
XHR Exclusion Pattern | URL filter for excluding XHR calls from monitoring. Use a semicolon (;) as a separator to enter multiple patterns such as .*foo.*; .*bar.* See Filter XHR Calls by URLs for details. |
API Key | This value is obtained when Browser RUM is set up. |
Cross domain correlation | Flag to enable session correlation across multiple domains. See Session Correlation Across Multiple Domains for more details. |
Inject at end of HEAD block | ABAP Agent injects JavaScript Agent snippet at the start of the HEAD block of the instrumented web pages. When this flag is set, the snippet is injected at the end of the HEAD block. This option is intended for troubleshooting. |
UI5 Instrumentation active | Flag to enable instrumentation of SAP Fiori (UI5) applications using the JavaScript Agent. |
WebDynpro instrumentation active | Flag to enable instrumentation of WebDynpro applications using the JavaScript Agent. |
WebGUI instrumentation active | Flag to enable instrumentation of WebGUI (SAPGUI for HTML) applications using the JavaScript Agent. |
BSP instrumentation active | Flag to enable instrumentation of BSP pages (also covers CRM WebUI) using the JavaScript Agent. |
EUM correlation is active | Flag to enable correlation between Browser RUM monitoring and SAP (C++ SDK) business transactions is available as of release 21.2.0. See Limitations. |
Custom Code Snippet
The Custom Code Snippet hosting option allows you to use more options like specifying the on-premise EUM server. See Configure the JavaScript Agent for details.
Choose Custom snippet from the Hosting Options dropdown menu and enter the custom snippet for the JavaScript Agent injection.
config.userEventInfo = {"PageView": function(context) {return {userData: {Instrumentation: "&INSTR_ID&", UserID: "&USER_ID&", Email: "&EMAIL&", Name: "&NAME&"}}}};
Name, full name and e-mail are affected by PII filter set in instrumentation in transaction /DVD/APPD_INSTR → Snapshot settings. For more information see: user data propagation
Limitations
Support | Limitation |
---|---|
C++ SDK / HTTP SDK correlation |
|
SAP NetWeaver instrumentation | Browser instrumentation is supported from SAP NetWeaver release 7.40. |
WebDynpro Applications | WebDynpro applications started via the Internet Explorer run in compatibility mode, which causes newer versions of the JavaScript Agent to end with syntax errors when trying to instrument the source code. The latest compatible JavaScript Agent 4.5.7.1910. Specify this version in the settings if you use the Internet Explorer for WebDynpro applications. |
Known Issue with Fiori Launchpad
The JavaScript Agent may prevent some Fiori Launchpad pages to be loaded incorrectly when XHR request monitoring is enabled. To ensure all Fiori Launchpad pages load correctly, follow the workarounds below based on what JavaScript Agent version you have.
JavaScript Agent >= 21.6.0
With JavaScript Agent >= 21.6.0, you must pass config.isAbapApp = true
:
(function(config) {
config.isAbapApp = true;
}
With ABAP Agent >= 21.8.0, this parameter is automatically added to the default snippet.
JavaScript Agent <= 21.5.0
With JavaScript Agent <= 21.5.0, you must exclude the XHR calls from monitoring by:
- Entering the value
.*
into the XHR Exclusion Pattern field in the SAPUI5 settings.
Or
- Add the following to the JavaScript custom snippet:
(function(xhr) {
xhr.exclude = {
urls: [{
pattern: ".*"
}
]
};
})(config.xhr || (config.xhr = {}));
See Filter XHR Calls by URLs for more details.