b2c-logging

You can implement structured logging in B2C Commerce scripts using the dw/system Logger and Log APIs. Get a logger for a specific category like 'checkout' and log messages at appropriate log levels to improve observability and troubleshooting.

Yes, you can create custom named log files in B2C Commerce by using the Logger.getLogger(prefix, category) method. This allows you to route logs to specific files for easier debugging and modular log management across transactions.

Category-based logging uses getLogger to assign log messages to modular categories. You can configure log levels per category directly within Business Manager, giving you granular control over log output without changing server-side code.

Nested Diagnostic Context (NDC) tracing correlates log messages across a single request in B2C Commerce. Use the dw/system logging APIs to push context information, helping you trace the flow of transactions like checkout and order processing.

Yes, B2C Commerce supports both static and instance logging. The dw/system Logger and Log APIs allow you to call logging methods statically or instantiate loggers, providing flexibility for different server-side scripting requirements.