Creating / Viewing a Raw Fiddler Capture

When using Universal Migrator to inject data into a destination system, it is possible that you may run into a bug in either Universal Migrator or in the API you are injecting into.  If you get API errors and the data seems correct, please sent us a Fiddler capture for review.

Please note that after you start running Fiddler, you must fully exit and reopen Universal Migrator in order to capture requests.

What is Fiddler?

Fiddler is an application that can monitor commands sent from Universal Migrator to an API.

 

First-Time Fiddler Setup

The first time you run Fiddler, there is some extra setup you must do.

  1. Launch Fiddler from inside Universal Migrator.
  2. If Fiddler is not installed, a web browser will open and start downloading it.  Install it and then re-launch Fiddler.
  3. In the dialog that appears, click Cancel


  4. Click on Rules and ensure the following options are checked:
  5. Click Keep and change it to 1000 Sessions.
  6. Click on Tools > Options > HTTPS and Check "Decrypt HTTPS Traffic".  A series of prompts will appear.  Allow them all.
  7. Click on the Protocols text:

    And in the dialog that appears, set it to the following value:
    <client>;ssl2;ssl3;tls1.0;tls1.1;tls1.2
  8. Click OK to close all dialogs.
  9. (OPTIONAL)  Apply a filter by clicking on Filters > Use Filters > Show Only the Following... and providing a value that represents the API host name you need to troubleshoot:

Isolate an Offending Record

Before doing an injection you should find the record in your database and isolate it by running a command similar to the following:

UPDATE
__M_Contacts
SET
Batch_Number = -1 --This should make the record run first.
WHERE
ID = 'SOME ID HERE'

This will allow you to inject a single record using Universal Migrator and will not clutter your view.

Once you have a record isolated and do an injection, you will see information appear in fiddler.

Understanding the Logs

When you look at a Fiddler trace, you will see something similar to the following.  The important parts are mentioned below:

On the left are commands that your computer sent.  Look for commands that are sent to the system you are injecting into and pay close attention to any red errors that have a code of 4XX or 5XX.  These likely indicate where the problem is.

In the top right, click the RAW tab.  This will show you the raw request that was sent from your computer to the API.  You should look it over and make sure everything looks right.

In the bottom right, click the RAW tab.  This will show you the raw response that was received.  This will likely have the error message and (ideally) any details on what went wrong.  If all you receive is an error like "Something went wrong" then you should definitely reach out to the API support team for the application you are injecting into.

Providing Logs

In order for us or your API vendor to be able to investigate this further, you will need to provide us with the logs you just collected.  To do this:

  1. Use CONTROL+CLICK to select the relevant messages.
  2. Right-Click and choose Save > Selected Sessions > In Archive Zip.
  3. Save the file and email/share it with us.

Once you have provided the logs, we will be able to determine if this is an issue in Universal Migrator or the API you are injecting into.

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.