Once an extension user submits recorded traffic, the log uploads to the Fiddler Jam cloud space, also known as the Jam portal. The Jam cloud space keeps any submitted logs in the storage for 30 days. After that period, if the log is not added to a workspace, it will be automatically deleted. With the help of the Fiddler Jam portal, any portal user with access rights could save, organize, analyze and work with the provided records.
After a Fiddler Jam user submits a log, the log uploads to the Fiddler Jam cloud space. At this moment, only this user knows the exact address of the log. The next step is for the extension user to share the generated link with other portal users (e.g., a support engineer with Fiddler Jam portal subscription and user role). The access rules are set via the link generation options.
Fiddler Jam protects the content of any submitted log through the following rules:
- All Jam logs are captured with applied masking for any data considered sensitive.
- The submitted log can be opened only by a portal user who meets the access rights requirements set by the extension user via the link generation options).
- The submitted log can be added to a workspace. Any Jam log that is not added to a workspace will be automatically deleted after 30 days.
For a portal viewer role to be able to open the submitted log, the log must be added to a workspace (by a portal user), and the extension user should have set an appropriate access level during the link generation.
Once a submitted log loads in the Fiddler Jam portal, there are multiple functionalities that the portal UI provides like:
- Use and edit the log's details (title, description, etc.).
- Investigate the log's captured traffic in detail (requests and responses) - Session data that includes the headers & bodies of each HTTP/HTTPS request and response.
- Inspect the browser events - Each Jam log contains the browser events triggered from user interactions with the page during the recording.
- Inspect the taken screenshots- When the extension user explicitly enables the screenshot option, a new screenshot is added for each user interaction (on a clickable element).
- Inspect the screen recording - When the extension user explicitly enables the Capture Video option, the whole capturing process from start to end is outputted in the Screen Recording tab.
- Analyzing the developer's console logs - When the extension user enables the Capture Console option.
- Deep-dive investigation through Fiddler Everywhere.
- Exporting as HAR file.
- Adding submitted logs to organizational workspaces.
The extension's capture options also allow you to mask sensitive data (like cookies and post-data) and disable the browser cache. Use the different Jam inspectors and tabs to debug and investigate any reported issue in detail.
Each Fiddler Jam log contains a list of entries containing different recorded information (HTTP/HTTPS sessions, console logs, screenshots, browser events, etc.). The log page in the Fiddler Jam portal has the following structure:
On the left side, the site provides two primary tabs called Storage Details and Captured Logs.
In the Storage Details, you will find lists of the entries stored in the Local Storage and the Session Storage. This tab will contain data only when the extension user explicitly used the Capture storage info from the Advanced options.
In the Captured Logs, you will find a numerated list of the captured HTTP/HTTPS sessions, screenshots, browser events, and console logs.
On the right side, the site provides two tabs called Screen Recording and Inspectors.
In the Screen Recording, you will find a screen recording from the browser (taken during the Jam recording). This tab will contain data only when the extension user explicitly used the Capture video from the Advanced options.
In the Inspectors tab, you will see an inspector that loads the information for the selected line from the Captured Logs list. The inspectors are changed depending on whether you choose an HTTP session, console log, or browser event. For example, Fiddler Jam loads the Request and Response inspectors when an HTTP session is selected, the console log details screen when a console log entry is selected, and a browser event information inspector when a browser event entry is selected.
To investigate a specific HTTP/HTTPS session:
- Open the submitted log.
- (Optional) Filter by search term (while using the Search text field) or Filter by log type (while using the Filter button)
Select a session line from the Captured Logs tab.
- When the selected line is an HTTP session, then the Request and ** response** inspectors load the session content (headers, body, cookies, etc.). Note that depending on the capture options, some of the submitted information might be masked.
- When the selected line is user interaction, the inspector will load technical details about the action (for example, the HTML tag, the text value, and the name of the4 specific action).
- When the selected line is a screenshot of user interaction, a preview inspector will load the taken screenshot depicting the moment of the user interaction alongside technical data about the action.
- When the selected line is a console log, a details inspector will load the log details and the captured stack trace.
Each captured HTTP(S) session has a unique line ID that can be used as a reference in both the Fiddler Jam portal and the Fiddler Everywhere desktop application.
The traffic list and the inspectors are inspired by the Fiddler Everywhere UI. Learn more about using the Request and Response inspectors to investigate the captured traffic.
Each Fiddler Jam log contains browser events that are triggered by user interaction. Each event stores additional information about the exact moment it happened (date and time) and the specific technical data (associated with the event). Additionally, the click events contain a screenshot with an action pointer.
The tracked events are as follows:
- navigated to
- tab opened
- tab closed
- pressed "Enter" key
- pressed "Tab" key
- scroll events
- text-input (just the event without the actual inputted data).
When the option Capture screenshots is explicitly enabled, the Fiddler Jam log will also contain screenshots for user interactions.
Steps needed to examine a screenshot:
- Select a Click event line from the Captured Logs list, and the associated screenshot loads in the Inspectors tab as the last property of the event data.
- Use the Save icon to download the screenshot locally as a PNG file.
The Fiddler Jam extension will take screenshots on user interactions like following a link, pressing a button, and other clickable events recognized as such by FIddler Jam.
Example of captured click action
A Fiddler Jam log will also contain console log lines if the extension user has explicitly enabled the developer's console logs capturing. Select a console logline from the Captured Logs list, and the chosen console log loads in the Inspectors tab. The inspector shows the time the log was outputted and the log stack trace content.
Example of captured console log
When the extension user explicitly enables the video recording, the whole capturing in the initial tab is output in a video recording. Load the video in the Screen recording tab to the right.
Example of captured screen recording
The Storage Details tab (to the left) displays the Local Storage and Session Storage data.
Example of captured storage data
Apart from the recorded data, each log also contains user-defined log details such as the log title, description, submitted by field, and the workspace. Every Jam log also contains an immutable Details that stores technical and environmental data extracted from the extension.
To add or edit the log details of a newly submitted log:
- Open the submitted log and click on Add to Workspace.
- In the prompted window, edit the log details (title, description, submitted by, workspace).
- Click Done when ready to add the log to the selected workspace with the new details.
To edit the details of a log that is already added in a workspace:
- Open the submitted log from the workspace.
- Click on the Edit Log Details icon (top-right corner next to Open Workspace).
- Edit the log's title, description, and submitted by fields.
- Click on Done when ready.
The Details expandable window (to the right of the Jam log title) shows the technical and environmental data extracted from the Jam extension. That includes information about the URL, time, OS, browser, screen resolution, used localization, timestamps, Jam extension version, and the enabled extension capture options.
Each Jam log loads on a screen with different tabs, and each tab has its conceptual inspectors. Learn more about using the log tabs and inspectors in the Jam Log Tabs and Inspectors section.
A Fiddler Jam log could contain an excessive number of recorded HTTP requests, browser events (mouse interactions and navigation events), screenshots, console logs, etc. Use the Search field in the Captured Logs tab to filter the entries based on a custom search term. Use the Filters (the icon next to the search text input) to filter out the different log entries (requests, screenshots, browser events, and console logs).
A submitted log can be exported as a HAR file (The HTTP Archive format, or HAR, is a JSON-formatted archive file format for logging a web browser's interaction with a site) and consequentially used with any 3rd-party software that supports HAR. Use the Download HAR File button (the icon to the Filters icon) to download the Jam log as a HAR file.
Any submitted log can also be re-loaded in the Fiddler Jam extension for a mock replay. Use the Load HAR for mocking button to load the log in the Fiddler Jam extension.
Any Jam log can be loaded in the standalone Fiddler Everywhere application for further deep-dive investigation. Learn more about Fiddler Everywhere and its cross-platform functionalities from the official documentation.
A submitted log can be re-shared via the Copy URL button (top-right corner next to the Submitted by).