Lab 2.3: Troubleshooting Application Response Time Browser
----------------------------------------------------------

.. note:: Estimated time to complete: **5 minutes**

.. include:: /accesslab.rst

Tasks
^^^^^
1. Login as **paula** in BIG-IQ.

2. Select application service ``security_site16_boston`` located under ``airport_security`` application. 

The virtual IP address ``10.1.10.116`` is configured behind ``site16.example.com`` FQDN.

3. Open Google Chrome in the **Ubuntu Jumphost** and navigate on the website ``http://site16.example.com/f5_browser_issue.php``.

.. note:: Accept the private certificates.

A page f5_browser_issue.php is behaving differently on Chrome compare to other browsers.

.. image:: ../pictures/module2/img_module2_lab3_1.png
   :align: center
   :scale: 40%

|

4. Back to BIG-IQ Application dashboard, open application ``security_site16_boston`` and display the *Application Response Time* Analytics.

Expand the right-edge of the analytics panel to get the URLs and Browser filters. Order the URLs by App Response Time Average.

.. image:: ../pictures/module2/img_module2_lab3_2.png
   :align: center
   :scale: 40%

|

If the Application Response Time column isn't showing, click right on the blue portion of the table, 
select Columns, then select Avg under the Application Response Time:

.. image:: ../pictures/module2/img_module2_lab3_2a.png
   :align: center
   :scale: 40%

|

5. Select the page **f5_browser_issue.php**, which has the highest value. Now all the values in all the other tables are about the page previously selected.

In the Browsers filter, notice the **30 seconds** Application Response Time for Chrome browser while other browsers show a much lower value.

.. image:: ../pictures/module2/img_module2_lab3_3.png
   :align: center
   :scale: 40%

We know now the problem with this web application isn't realated to F5 but to the application itself.