Summary:

This article describes the installation, configuration, and usage of Fiddler application for gathering further information when users are experiencing performance issues, like slowness in the application, or communication errors.

To further investigate performance-related issues in detail we need to trace HTTPS traffic from the browser of the user who is experiencing the issue.
The user is required to install, configure, and start the Fiddler application and proceed to perform the operation which is reported to be causing issues, such as opening an invoice, viewing invoice image, logging into the service, or transitioning between screens.

We will perform a traffic packet test to gain a granular understanding of what calls are taking an extended period in relation to the lagging operation reported by the end-user.

Fiddler installation and configuration steps:

1. Install Fiddler application from following URL: https://www.telerik.com/download/fiddler.
   Following web page will open when the installation is complete.
   
   
   
   NOTE! The setup program needs to be run as an administrator.
   If the administrator account used to run the setup program is different than the current user, then the web page will open empty and Fiddler application cannot be found from the Start Menu.
   
   
   
   This is because the application is installed under the user that runs the setup program and shortcuts are also created under that user.
   In that case, copy the shortcut from the adminuser folder "C:\Users\adminuser\AppData\Roaming\Microsoft\Windows\Start Menu\Programs" to the same folder under the current user account.
   
   
2. Open Start Menu and start the "Fiddler 4" application.
   
   
   
   
3. Before starting the traffic capture, one setting must be checked in Tools -> Telerik Fiddler Options.
   
   
   
   
4. Set Fiddler to capture and decrypt HTTPS traffic as highlighted below.
   
   
   
   
5. You can also turn on filtering to capture only P2P related traffic. Filters can be found from the right side of the screen.
   Select Use Filters and Show only the following Hosts. Enter the host part of the P2P url: tenant.p2p.basware.com.
   
   
   
   
6. Now you are good to go. You can turn HTTPS traffic capturing on/off with F12 key.
   When traffic is captured, lines appear to the UI and there is Capturing logo on the bottom left hand side.
   
   
   
   
7. Once you have started capturing the traffic, you can start using P2P and reproduce the issue.
   It is best to first start the capturing and then log in to P2P.
   
   
8. Traffic log can grow quite big during long period of usage, so after around 15 minutes of usage (or after the issue has reoccurred) we should have enough data.
   Log out from P2P before stopping the capturing.
   
   
   
   
9. Stop the capturing and save the log to a file.
   
   
   
   
10. Give the .saz file a recognizable name with username on it.
    
    
    
    
11. At the end of the capturing the sessions zip these .saz files and send them to Basware Support via the Support Portal for further analysis.
    We would also recommend you to fill in the attached Excel file Alusta SaaS P2P - UI Performance Issue - Template Form.xlsx to provide additional background information for the investigation.