Logging EBS order Sync via app builder

[astikunagar]

Current Scenario

we can only see the journal fetching and 0 entires logs for ebs-sync

Expected Outcome

EBS order sync important information like request body and response should be available in app builder logs

Image for reference

[dylandepass]

We should not be logging request bodies with PII and Payment data. This is not a good idea.

What is the requirement here @awasthiruchi?

[awasthiruchi]

@dylandepass I agree that we should not log request bodies containing PII or payment data.

However, we still need enough information to troubleshoot integration issues. For example, we've had cases where the SOA Composite was unavailable, and we've also seen failures caused by invalid or unsupported special characters in the request payload. Without the request and response details, it's very difficult to determine later whether the issue was caused by the payload, a validation error, or an upstream service outage.

Could we log sanitized versions of both the request and response instead? We can redact or mask all PII and payment-related fields while retaining the non-sensitive fields, response status, error code, error message, and correlation/request ID. This should provide enough information for troubleshooting without exposing sensitive data.

FYI - @astikunagar @sumitverma13

[maxakuru]

@awasthiruchi

Couple things here:

1. you're looking at the Production app builder logs, but everything is on Stage right now. Use the dropdown in the left column to select the other workspace. There will always be 0 entries in Production for now.
2. we can log redacted req/res pairs, but those will only include the calls to the Commerce API. If the errors are coming from dependencies we won't see those logs regardless of what we do here.

Are we expecting these errors to be issues with Commerce API? If not, the place to look would likely be the Journal API

[awasthiruchi]

@astikunagar Can you check this?