Run log inspector

Log inspector shows you a detailed, ordered set of operations (read about operations) which a given log underwent during processing.

You can use log inspector to dig into the nitty gritty of how data looked at a given point in time during log processing. You can use this for troubleshooting to find where or what might have gone wrong with a failed log, or you can use this during implementation to understand how your subscription settings are working.

1. Log in to the Redox dashboard.
2. From the navigation menu, click the Logs page.
3. By default, the search bar and filters display, along with any logs from the last seven days. Use search terms, filters, or a combination of both to find the log you want to investigate. Click the relevant log in the list.
4. The log details display on the right, which includes the log ID and the processing stages the log went through. Click any of the log stages to view details for a given stage.
5. To investigate log processing in more detail, click the Log inspector button. You won't see this option if you're not assigned to an engineer or support role.
6. Log inspector runs and opens a new page with the source, destination, timestamp, and operation details (review operation types). Operations display in sequential order.

   Changes to subscription settings

   Log inspector uses current subscription settings. These may or may not be the same settings that applied to the original log. If you (or a Redoxer) have made changes to the subscription since the time the log ran, log inspector will use the most recent settings, not necessarily the original settings that were used for the log.

   Differences in delivery operation

   Since log inspector is a troubleshooting tool, there are slight differences in processing. Mostly, this applies to the delivery operation, which is the point when a request is sent to the target destination.

   Redox doesn't actually send the request to the destination with log inspector. Instead, the delivery operation details shows contents from the original log. For example, if the original log failed to send to a destination due to a timeout error, log inspector will always show a timeout error at that operation.

7. From the lefthand menu, select an operation to view its details. The details may include operation metadata (e.g., identifiers, owners), request and response metadata, and any payload snapshots.

   Who last updated an operation

   You'll only see the name of the user who last altered the operation if you both belong to the same organization.

   If you don't belong to the same organization, the user who last altered the operation isn't shown.

   If a Redoxer last altered the operation, the user's name is generalized to Redox for employee privacy.

8. Review any diff views in the payload snapshots for any operations. Input payload snapshots show what the data looked like before the operation began, and any output payload snapshots show what the data looked like after the operation ran. This will help you narrow down where an unexpected error or change occurred during processing.

   Tip about errors

   If there’s an error in the deliveries step, you may assume there was a failure during Redox processing (i.e., in building the request or translating the response). However, if the response field shows an actual reply object, it means that Redox successfully delivered the request but the destination sent back an error.

   Please know this isn’t us pointing fingers. Since knowledge is power, we want you to know where the error occurred so you can better troubleshoot.

9. Modify any settings and re-run log inspector by either clicking the Run log inspector button or refreshing the page.