Collecting a Fiddler or HTTP session for UEM issues

Using Fiddler to create an HTTP session of the application monitored

Occasionally, we will need more information around the injection of our javascript agent. This can also provide information around the behavior of the application and the dynaTrace Monitor signal. Please follow the steps below to obtain the session archive from the Fiddler application.

  1. If you do not have fiddler installed on you will need to visit the site to install (http://www.telerik.com/download/fiddler)
  2. If your site is running as HTTPS please follow these configuration steps first:
    1. With Fiddler open, find Tools > Fiddler Options...  and set the checkboxes below:
  3. If the Application is an Android application, please follow these configuration steps first:
    1. Set Fiddler as the Wi-Fi proxy, as seen below (Settings > Wi-Fi > Modify Network). Obtain your workstation IP by using "ipconfig" in Windows and "ifconfig" in Linux in the Command Line. And you can obtain the Proxy port by looking in Fiddler (Tools > Fiddler Options > Connections).
       
    2. If the Application uses SSL Certificates, you must also add the Fiddler Certificate to your device.
      1. Obtain the Fiddler Certificate by going to Tools > Fiddler Options > HTTPS > Actions > Export Root Certificate to Desktop.
      2. Use the exported Certificate, usually named FiddlerRoot.cer, and add it on your Android device by going to Settings > Security > Install from SD card (copy the Certificate to your device first). You should then see the Certificate as a Trusted User Credential:
  4. To start, you will need to turn OFF capturing so that the browser cache can be cleared to start a fresh trace.
    1. File > Capture Traffic or press F12.
    2. Clear your browser cache so all cached items are removed and require a re-download of the content.
  5. Now start Capturing Traffic again and complete the problematic transaction on your page.
  6. Once completed, Save All Sessions.
  7. Upload the file to the support ticket for the Solution Engineer to review.

Alternatives to fiddler session

There are two alternatives if for some reason you are not able to create a fiddler session.

Using chrome's Dev Tools to export an HTTP Archive Session (HAR)

This alternative should be seen as last option. It's always best to create a fiddler session (see above) because with a fiddler session it's easier to reproduce the support case.

In the event that fiddler can't be used to create the session, Google Chrome can export a session for review as well.  Please see the steps below to collect the HAR file

  1. Open Google Chrome and clear the browser cache.
  2. Press F12 to open the Dev Tools.
  3. Click on the Network tab.
  4. Complete the problematic transaction on your application.
  5. Once complete, select all sessions and right-click in the blank space to select Save as HAR with Content.
  6. Upload the file to the support ticket for the Solution Engineer to review.

Using IE's Dev Tools to export an NetXML session

This alternative should be seen as last option. It's always best to create a fiddler session (see above) because with a fiddler session it's easier to reproduce the support case.

  1. Open Internet Explorer 8+ and open the developer toolbar with F12
  2. Clear the cache and domain cookies
    .
    1. Clear the cache with .
    2. Clear the cookies with .
  3. Press the Play button  to begin the trace.
  4. Complete the problematic transaction on your application.
  5. Once complete, select the Export button  to save the file.
  6. Upload the file to the support ticket for the Solution Engineer to review.