As an application specialist, you can set up monitoring of end-user data from any kind of HTML pages by manually inserting a JavaScript stub in your applications. You might want to use this option for one of the following reasons:
When you manually set up end-user monitoring, you can collect data such as the number of users, end-to-end transaction time, and errors. For more information about collected end-user data, see Analyzing user transaction details.
Note
The topic presents the following:
All components of the App Visibility server—the portal, collector, and proxy—must be installed.
Consult with your system administrator to obtain the following information:
apm_proxy_host
value. The property value must be the host name or IP address of the load balancing server. Use this method if your application is already in the TrueSight console as a manual application. If your application is not yet in the console, see To open and prepare the JavaScript from the App Visibility proxy.
Open the file in a text editor.
The file contains the following script:
The appId value is unique to the specific application.
The following values are automatically replaced with values from the App Visibility proxy. You can change the values if you want to connect to a different proxy.
To add the JavaScript stub to your application, see To manually insert the JavaScript, below.
Use this method if your application is not yet in the TrueSight console.
Note
If your application is already in the TrueSight console, do not use this method to add end-user monitoring. Instead, see To open and prepare the JavaScript from the TrueSight console.
Otherwise, you see two applications in the console that have the same name.
A file with the following script opens:
application_name
placeholder with a meaningful, unique application name, and remove the comment indicators (//). application_name
in the stub, a value is assigned through application discovery rules. entrypoint_name
placeholder with a meaningful entry point name, and remove the comment indicators (//). entrypoint_name
in the stub, the user transaction name is automatically assigned. apm_proxy_http_port
is the port number of the HTTP beacon receiver (default value is 880). apm_proxy_host
is the host name or IP address of the App Visibility proxy. apm_proxy_https_port
is the port number of the HTTPS beacon receiver (default value is 8444).src
) value, replace the value of apm_proxy_host
with value from the App Visibility proxy, and the value of either the apm_proxy_https_port
or the apm_proxy_http_port
, depending on your system.To add the JavaScript stub to your application, see To manually insert the JavaScript, below.
<head>
element contains a <script>
element, insert the stub before the first <script>
element.<head>
element does not contain a <script>
element, insert the stub at the end of the <head>
element, before the closing </head>
tag.Save the page.
Ensure that the script appears in you application's web pages.
After you complete the manual set up for end-user monitoring, perform the following configuration tasks:
(Infrastructure Management) You can edit an application model for an application with a manually inserted JavaScript stub. Edit the application in the same way you would other manually created application models.
After configuration is complete, you can analyze end-user experience with the User tier.
Setting up applications for monitoring
1 Comment
Sara Kamen