Monitor Browser Response Time

The Browser Agent lets you monitor web page load performance metrics. You can pinpoint the performance degradation to the browser, network, or the application server.
apmdevops102
The Browser Agent lets you monitor web page load performance metrics. You can pinpoint the performance degradation to the browser, network, or the application server.
As an application owner, follow these high-level steps:
  1. Read and use this additional information that is specific to the Browser Agent:
Analyze Browser Agent Metrics
You can view live data in the Investigator, or you can select a range of time to view historical data. In the Metric Browser tree, the Business Segment node under the SuperDomain node shows the browser response time metrics.
Note:
 Due to how browsers operate (for example, caching resources and preloading web pages), the Responses Per Interval for frontends might not match the Responses Per Interval for the Browser Agent.
Follow these steps:
  1. In APM Team Center, click
    WebView
    .
    APM WebView appears.
  2. Click
    INVESTIGATOR, Metric Browser
    .
    The Metric Browser tab lists metrics and other information in a tree format. The high-level nodes immediately under domain nodes represent agents that are installed on individual application server hosts or the equivalent. A node is where specific metric information is gathered and displayed in the agent-centric tree view. When you expand a node, you can view and search more detailed metric information.
  3. Expand the SuperDomain or Domains node in the Metric Browser tree depending on your environment.
    The tree view of agents, resources, and metrics refreshes every 15 seconds to show current metric data.
  4. View browser metrics by navigating the nodes under the Business Segment node, for example:
    Business Segment | Bookstore | Login via Chrome | <
    Business_Transaction_Component
    > | Browser | 
    Metrics
    • The W3C Navigation Timing metrics appear.
    • The AJAX dynamic web page metrics appear under the Browser node in a separate folder.
    • The JavaScript Function metrics appear under the Browser node in separate folders:
      • Average Execution Time: The average time for the JavaScript function to execute.
      • Invocation Count Per Interval: The total number of times the JavaScript function was invoked.
  5. Analyze events and other data by clicking the tabs in the right pane.
    For example, click the
    Errors
    tab to detect application errors.
View Individual Components in Trace View
Transaction traces record the Browser Agent-specific attributes that browser response time monitoring passes. You can view the transaction components in a graphical stack. You examine the components from top to bottom to understand the sequence of calls within a time period and evaluate performance. Browser response time monitoring metadata attributes are associated with the root component.
Follow these steps:
  1. In APM Team Center, click
    WebView
    .
    APM WebView appears.
  2. Click
    Tools, Transaction Tracer
    .
  3. Select a transaction trace in the table.
  4. Click the
    Trace View
    tab in the lower pane.
    Note
    : In Live mode, Traces tab lists transaction trace events from the last 20 minutes. Transaction trace event older than 20 minutes are not displayed in live mode.
  5. Select and expand the transaction trace event that you want to investigate.
  6. In the Component Details area, view the following information:
    Note:
    Not all the information is available about deep transaction trace components. These Introscope transaction trace properties are examples.
    Application Name: /
    Class: weblogic.servlet.FileServlet
    Context Path: /BRTMNameApp_DynamicJSI
    BrowsGUID: 2DED74850A89B0AF0054E73F598BC478
    HTTP Method: GET
    Method: service
    Scheme: http
    Server Name: demo.name.com
    Server Port: 7001
    Thread Group Name: Pooled Threads
    Thread Name: [ACTIVE] ExecuteThread '1' for queue: 'weblogic.kernel.Default'
    Trace Type: Normal
    URL: /BRTMNameApp_DynamicJSI/index.html
    The following browser transaction trace properties are examples:
    Metrics (with their business segment paths-not shown) for example:
    Average Browser Render Time (ms)
    Average Connection Establishment Time (ms)
    Average DNS Lookup Time (ms)
    Average DOM Construction Time (ms) 
    Average Page Load Complete Time (ms)
    Average Previous Page Unload Time (ms)
    Average Round Trip Time (ms)
    Average Time to First Byte (ms)
    Average Time to Last Byte (ms)
    Responses Per Interval
    BrowsGUID: E1BCF2010A892C82600A4972A893F2430
    Trace ID: 1429716404889:60
    Trace Type: Normal
    browser type: Chrome
    browser version: 42
    duration: 130
    geo-location: -255,-255
    startTime: 1429716398593
  7. Determine the root cause of the application performance problem.
    Use the identifying information in the available tabs and gather specific details about the problem.
    View these fields: Timestamp, Duration, Description, UserID (if any is associated with the problem).
  8. Identify the components that appear to cause the problem, and then follow the issue resolution process for your organization.
Query for Correlated Events
In Introscope, you can query for events that are correlated -- the events that are part of the same larger transaction. For example, a browser response time event is correlated with a servlet transaction event. When you generate transaction traces with the Browser Agent enabled, it creates both Introscope traces and Browser Agent traces that CorBrowsGUID links. The following properties affect how the browser trace is correlated with the Introscope trace:
introscope.agent.browseragent.checkHeadFilterPresence.enabled=TRUE
Sets a flag back to the browser to send browser transaction traces where the correlation ID is set correctly. This action occurs when the Java agent is executing a transaction trace session by opening up the transaction trace session window. This property is not included in the IntroscopeAgent.profile file; add it manually to change the setting.
introscope.agent.browseragent.checkTailFilterPresence.enabled=TRUE
Sets a flag back to the browser to send browser transaction traces where the correlation ID is set correctly. This action occurs when the Java agent is executing a transaction trace session and it is using a timing threshold session. This property is not included in the IntroscopeAgent.profile file; add it manually to change the setting.
Even if a transaction type event is selected, both transactions and errors can be returned in the results.
Follow these steps:
  1. In WebView, select
    Tools, Historical Event Viewer
    .
  2. The Historical Event Viewer opens.
  3. In the Query field, enter
    CorBrowsGUID
    with the ID of the trace you want to view, for example:
    CorBrowsGUID:2DED74850A89B0AF0054E73F598BC478
  4. Click
    GO
    .
    The standard trace event information (number of events) appears in the viewer.
  5. Analyze transaction times and find the root cause of slow times by using the viewer.
Monitor Sustainability Metrics
The Agent Stats node displays sustainability metrics about the internal state of the agent rather than the application the agent is monitoring. This data can help you investigate agent behavior.
Note:
 Each sustainability metric value is based on the assigned value for the corresponding Browser Agent business transaction monitoring property. The IntroscopeAgent.profile file includes these corresponding properties.
Follow these steps:
  1. In APM Team Center, click
    WebView
    .
    APM WebView appears.
  2. Click
    INVESTIGATOR, Metric Browser
    .
    The Metric Browser tab lists metrics and other information in a tree format.
  3. Expand the SuperDomain in the Metric Browser tree depending on your environment.
    The tree view of agents, resources, and metrics refreshes every 15 seconds to show current metric data.
  4. Navigate to Agent Stats > Sustainability > Browser Agent Business Transaction.
    The following Browser Agent sustainability metrics appear:
    introscope.agent.browseragent.ajaxMetricsEnabled
    introscope.agent.browseragent.ajaxMetricsThreshold
    introscope.agent.browseragent.browserLoggingEnabled
    introscope.agent.browseragent.contentencoding.enabled
    introscope.agent.browseragent.enabled
    introscope.agent.browseragent.excludeURLList
    introscope.agent.browseragent.geolocation.enabled
    introscope.agent.browseragent.geolocation.highAccuracyEnabled
    introscope.agent.browseragent.geolocation.maximumAge
    introscope.agent.browseragent.geolocation.timeout
    introscope.agent.browseragent.includeURLList
    introscope.agent.browseragent.jsFunctionMetricsEnabled
    introscope.agent.browseragent.jsFunctionMetricsThreshold
    introscope.agent.browseragent.metricFrequency
    introscope.agent.browseragent.pageLoadMetricsEnabled
    introscope.agent.browseragent.pageLoadMetricsThreshold
    introscope.agent.browseragent.resource.count
    introscope.agent.browseragent.resourceLimit
    introscope.agent.browseragent.snippet.maxSearchingLength
    introscope.agent.browseragent.snippet.maxSearchingReached.count
    introscope.agent.browseragent.snippetInsertionEnabled
    introscope.agent.browseragent.throttleResponse.count
    introscope.agent.browseragent.throttleResponseLimit
    introscope.agent.browseragent.unsupportedBrowsers.count
    introscope.agent.browseragent.urlMetricOff
    introscope.agent.browseragent.wilyURL
    Metric activity appears in 15-second intervals.
  5. Select a metric and view information about it by using the tabs in the right pane.