In Salesforce B2C Commerce, the dw.system.Logger.getLogger(String...) method is used to create custom log files. The filename convention for these logs is custom--.... The arguments passed to getLogger() define the category hierarchy. In the code Logger.getLogger(“products”,”export”), "products" is the primary category. The system generates a log file name based on this primary category, prefixed with custom-. Therefore, the filename begins with custom-products. The log level (INFO) and the active log category (root) determine which messages are captured, but they do not influence the naming convention of the custom log file itself.

1. Salesforce B2C Commerce Cloud Documentation

dw.system.Logger Class: "To create a custom log file

create a category that does not begin with one of the standard category prefixes... The file name is custom- followed by the category name

with dots replaced by hyphens." This establishes the custom- prefix and category-based naming. (Reference: Salesforce B2C Commerce Infocenter

Script API documentation for the dw.system.Logger class).

2. Salesforce B2C Commerce Cloud Documentation

getLogger(String...) method: "The categories are joined together with '.' characters to form a hierarchical category name." In this scenario

the full category is products.export. While the full filename would be custom-products-export...

the question and options simplify this to the primary category

making custom-products the most accurate choice among the given options. (Reference: Salesforce B2C Commerce Infocenter

Script API documentation for the dw.system.Logger.getLogger method).

3. Salesforce B2C Commerce Cloud Documentation

Log Levels: The documentation on logging and debugging specifies that log levels (e.g.

INFO

WARN

ERROR) are for filtering message severity and do not alter the log file's name. (Reference: Salesforce B2C Commerce Infocenter

"Logging" section under Developing).