Custom log file access, size limits and retention
Key Takeaway
Each application server can write up to 10 MB per day into a custom log file. At that limit, B2C Commerce writes the message "Maximum log file size per day reached, logging suspended." to the file and suspends logging to it until 00:00 GMT the next day.
When your B2C Commerce script code logs messages through the dw.system.Logger API, the messages go into custom log files on the instance. You read these files through WebDAV, either in Business Manager or in a WebDAV client. Each file has a daily size limit, and the files are deleted automatically after a set time. You need to know both limits, because they decide how much you can log and how long you can read it.
Custom log files and custom named log files
Custom log files are the files your script logging creates. Their names begin with "custom". The standard custom log files are customdebug, custominfo, customwarn, customerror, and customfatal. There is one log file per log level, per application server.
Logger.getLogger(fileNamePrefix, category) writes to a custom named log file instead. The first call with a prefix creates a log instance and a log file in the usual log directory. Later calls with the same prefix return that same instance, so all their messages land in the same file.
Unlike the standard custom log files, which split messages into a separate file for each log level, a custom named log file holds every message for its log category in one file, whatever the log level.
A custom named log file follows the pattern custom-<file name prefix>-<hostname>-appserver-<creation date of the file in GMT>.log. The file name prefix has strict rules:
- It can't be null or an empty string.
- It must be 3 to 25 characters long.
- It can use only a-z, A-Z, 0-9, hyphen, and underscore.
- It can't start or end with a hyphen or underscore.
// Running on hostname blade0-1 on 30 October 2026 (GMT)
var exportLog = Logger.getLogger('orderexport', 'export');
// => creates custom-orderexport-blade0-1-appserver-20261030.log
var sameLog = Logger.getLogger('orderexport', 'export');
// => returns the same log instance, so messages go to the same fileThe prefix orderexport is 11 characters long and uses only lowercase letters, so it follows the prefix rules. The first call creates the log instance and its file. The second call uses the same prefix, so B2C Commerce returns the existing instance instead of creating another file.
Each application server allows up to 200 different log file names per day through Logger.getLogger(String, String), which means 200 log instances and 200 log files. The logging.customLogFiles quota tracks this hard limit.