Redux trace contain actions and operations that your browser executed while the Redux trace was recording. This will often show us an errors and may give more information to us to track where the issue is in the code-base. It can also show us the time taken for different operations, so it can help with issues related to how fast (or slow) a page may load in a browser window.
The steps vary from browser to browser. These steps are applicable to desktop browsers on both Windows and macOS. This KB shows steps for most common browsers Chrome and Firefox. Steps for other browser should be similar.
Once the Redux trace has been generated, it’s good practice to zip the .json file and send it to us.