What is the difference between standard and trace logs in the Fabric Runtime?

HCL Volt MX Volt MX Forum
1
This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal.

I’ve read the docs twice, but it’s not clearly explained. Something about the trace logs being “between client and backend”? but in the standard ones I still see requests. I think the trace logs are a subset of the standard ones. Just the ones related to requests between the client app and Fabric. I don’t get why the docs mention the backend here. I’m asking about the Fabric server.

**Image removed for security reasons**

Looking at these to tabs. The presentation is clearly different. and I can see that trace logs are for requests only. I’d just like a more formal definition of the difference.

2

Trace logs have the full http request/response between the client app and Fabric Server

In Standard logs the first section allows you to capture the network response between Fabric Server and Backend as well unless you are using some template and preprocessor the traffic between client and Fabric and Fabric and backend will be pretty much the same..

Standard logs also has option for capturing traffic between client app and server logs in trace section go to database, whereas standard logs goes to file.

Standard logs = File, Trace logs = DB

Standard logs has option to specify lot of things, whereas trace logs is specific