Log Files

Log files capture information about system resources, performance, errors, and quotas.

B2C Commerce includes several different types of log files, including system logs, custom logs, import and export logs, a quota log, security logs, and batch processing logs.

To see system and custom application log files, click App Launcher and then select Administration > Site Development > Development Setup. In the WebDAV Access section, click the Log files links. The Log files home page (Index of /) shows a list of log files in alphabetical order. With the right permission, access the log files via a WebDAV client.

There are two types of log files:

• System logging: System information logging is turned on by default. Ask Salesforce Support to change your configuration if you want to change your system’s logging configuration.
• Custom logging: If you perform programmatic logging using script files, configure custom logging in Business Manager. Custom logging is turned on for certain types of messages. Configure it for the other types of messages. Custom debug and info logs are disabled by default. Enabled or disable them for a specific instance by clicking App Launcher and then selecting Administration > Operations > Custom Log Settings. If custom logging is disabled, no messages are logged. Custom log files begin with custom.

Production and Staging instance log files are captured daily, stored for 30 days, and then automatically deleted. The only exception is security log files, which are automatically deleted after 90 days.

Delete log files more frequently using WebDAV. After three days, the log files are moved into a log_archive directory and compressed into gzip files. If you want to retain log files for more than their retention time, download the files and store them locally.

Instead of downloading log files via WebDAV, use the B2C Commerce CLI] to stream and filter logs directly from your terminal. To install the tool and authenticate, see B2C CLI, MCP and Tooling SDK.

1# List available log files on the instance
2b2c logs list
3
4# Tail all ERROR- and FATAL-level entries in real time
5b2c logs tail --level ERROR --level FATAL
6
7# Tail only custominfo log files
8b2c logs tail --filter custominfo
9
10# Get the 200 most recent ERROR entries as structured JSON
11b2c logs get --count 200 --level ERROR --json
12
13# Search the last hour for a specific string
14b2c logs get --since 1h --search "NullPointerException"

For the full command reference, see Logs Commands in the B2C DX documentation.

Allowing files to grow indefinitely can cause performance and storage issues, so files are restricted by size. Each application server can write up to 10 MB per day into the customdebug, custominfo, customfatal, customerror, and customwarn log files. The same limit applies to the number of fatal, error, warn, debug, and info messages that can be stored in custom named log files.

To maintain optimal performance and stability, delete unnecessary log files as soon as possible. Don’t store more than 100,000 files in a single folder. If there are more than 100,000 files in a single folder, files are deleted starting with the oldest first even if the files are newer than the retention period for the folder. The 100,000 limit applies to files in one specific folder, not across subfolders.

A day is 00:00 to 24:00 (12:00 a.m. to midnight next day) in Greenwich Mean Time (GMT). Logging is suspended until the next day (00:00) once the 10 MB limit has been reached. If the maximum possible log size is almost reached, for example, the log file size is 9.9 MB, and the next log message will exceed the limit, the log message is still written, but only up to an additional 100 KB beyond the 100 MB. This uses the log content’s full permitted amount. When the log file has reached its maximum size for the day, the following info message is written to the log file:

1+++++++++++ Maximum log file size per day reached, logging suspended. +++++++++++

One log file exists per log level, per application server. Log levels for system and customization include:

• info
• error
• warn
• debug
• fatal

The debug log level is always disabled on production instances and enabled for in memory logging on non-production instances. In memory logging allows for the Show Request Log feature, but doesn’t generate log files.

This table describes how different log files work.

Error and Warning messages are tracked for redundancy. If a message appears more than 10 times in 3 minutes, it is suppressed if it reappears within the next 3 minutes. When suppression begins, the following text precedes the log message text within the log entry:

1The following message was generated more than 10 times within the last 180 seconds.
2It will be suppressed for 180 seconds:

Tracking of repeated messages continues while the suppression is in place. After the suppression period has ended, if a new log message appears whose occurrence rate is over the 10 message per 180-second threshold, it is logged with the message described. A new suppression period begins.

The method public static Log getLogger( String fileNamePrefix, String category ) obtains a log instance and writes to a custom log file through that log instance. When you call the method with the given file name prefix the first time, B2C Commerce creates a log instance and a corresponding log file in the usual log directory. When you call the method with the same file name prefix a second time, B2C Commerce returns the same log instance as the first call, and all log messages are stored in the same log file.

The log messages are written with the same pattern as used in system and custom logs, as follows:

1custom - <file name prefix> - <hostname> - appserver - <creation date of the file in GMT>.log

This is an example:

1custom-prefix-blade0-1-appserver-20110706.log

The file name prefix must follow these rules:

• Cannot be null or an empty string
• Must be at least three characters long
• Can contain characters a-z A-Z 0–9 ’-’ ’_’ only
• Can have up to 25 characters
• Cannot start or end with ’-’ or ’_’
• Can only start or end with a-z A-Z 0–9

The log categories provided through Business Manager for the custom script log are also applied to this type of logger.

The quota log contains B2C Commerce quota details such as:

• System object (data) quota status and limits
• System API quotas status and limits
• Sandbox system’s database status
• Name of deprecated methods and how often they were used within the last 24 hours

Security log files are located at https://<instance name>.demandware.net/on/demandware.servlet/webdav/Sites/Securitylogs.

Security log entries can look like this:

[2015-10-28 02:23:19.139 GMT][dw-sec] (User: ‘username’ (Sites), IP: 100.100.10.100 [LOGIN] : logged in.)

The security log also includes:

• The session ID to the log entry for Business Manager logins
• Log entries for re-logins (when the Business Manager requires the password due to inactivity). These log entries log both the old and the new session ID.

Security log files are automatically deleted after 90 days. Users and clients can’t delete security logs, or turn off security logging. If you want to retain log files longer than 90 days, you must download the files and store them locally or in a dedicated storage.

Find import and export specific information in the import and export log files. In Business Manager, click App Launcher and then select Administration > Site Development > Development Setup. In the WebDAV Access section, click the Import/Export link to view log details on any activity relative to import and export. This information can provide you with critical insight into job failures or data errors. Use this link or access the data via a WebDAV client when performing import and export functions via Business Manager or programmatically via a pipelet. Import and export can be performed on many types of data.

Analyze the data in these logs as part of daily operations and each time there is an issue with a related process such as catalog import, price book or custom feed.

The Import/Export directory has the following structure on all instances.

This directory contains logs for specific processes such as catalog, customer, or product batch processing, catalog import and export, inventory import, and price book import. It also contains validation logs for Price Book, Promotions, Metadata, Coupon, Inventory, and Catalog.

processlogs_archive/ Archive of logs

This directory contains import and export source files, which include processes such as catalog import and custom jobs for feeds such as affiliates and channel advisor.

The following is an example of a subdirectory structure for src/:

1activedata/
2affiliatefeeds/
3archive/
4catalog/
5catalog_archive/
6channeladvisor/
7customer/
8customization/
9customobject/
10export/
11instance/
12library/
13operations/
14order/
15upload/ (Directory for upload of files before processing)

Files in the /Impex folder and files in the /Impex subfolders are automatically deleted after 30 days. The subfolders are saved.

Perform batch processing on catalogs, customers, and products. Product/catalog batch processing and customer batch processing aren’t combined into the same interface. View the results of either from their respective Business Manager sections. For example, view customer batch processes by clicking App Launcher and then selecting Merchant Tools > site > Customers > Batch Processing, but not by selecting site > Merchant Tools > Products and Catalogs > Batch Processing.

Batch processing logs can contain error reports as a result of a failed batch process. A log file can contain WARN, ERROR, or FATAL log messages. View the logs from the specific Batch Processing page, or from the Import/Export log directory, for example:

1/Impex/log/Batch-Customer-20100128192425062.log

Access log files from Business Manager or a WebDAV client.

1. To access log files from Business Manager, click App Launcher and then select Administration > Site Development > Development Setup and scroll to the WebDAV Acess section, where you can click links to see the logs.

2. To access log files from a WebDAV client:

   1. Set up an SSL connection in Total Commander, using a valid Business Manager user name and password with proper access to connect to the Logs directory.

      Use any WebDAV client but we recommend Total Commander. Make sure to use the Total Commander WebDAV client and not the FTP client, as sFTP isn’t supported.

   2. Use the following URL to access the logs:

      https://{\<instance name>}/on/demandware.servlet/webdav/Sites/Logs

      When connected, browse logs, search for error strings, or download to your environment.

Quota log files aggregate quota messages over a set period. Messages are written when the warn threshold or limit of a quota is exceeded.

The code location of the most recent event is written to the log file. The code locations of the aggregated events aren’t exposed. Quota log files show information about the location where a quota-warn threshold or limit was exceeded. The information includes the site name, job name, and top pipeline name. Additional information is sometimes included about the executed pipelet, script, pipeline node, and template.

Quota log files use this general format:

• a timestamp
• the thread name (contains type of request, site, pipeline name, and other parameters)
• the actual message

This format produces log entries such as the following:

1[2012-05-23 13:00:22.577 GMT] [RequestHandlerServlet|14320460|Sites-SiteGenesis-Site|Product-Show|
2PipelineCall|pRLNN0PXCp7rqIClq7IcPUvuEEjtkOWUAMBdUWhniPRFlV4Xvim3HwhDw96bRZ7e5BUxhnkC2ExrVYZVBFLJtw==]
3Quota api.jsStringLength (enforced, warn 600000, limit 1000000): warn threshold exceeded 1 time(s),
4max actual was 600010, current location: request/site Sites-SiteGenesis-Site/top pipeline Product-Show/
5interaction node/template refapp.default_.CustomDisplay

This section of the entry is the timestamp:

1[2012-05-23 13:00:22.577 GMT]

This section of the entry is the internal reference:

1[RequestHandlerServlet|14320460|Sites-SiteGenesis-Site|Product-Show|PipelineCall|
2 pRLNN0PXCp7rqIClq7IcPUvuEEjtkOWUAMBdUWhniPRFlV4Xvim3HwhDw96bRZ7e5BUxhnkC2ExrVYZVBFLJtw==]

This section of the entry is the message:

1Quota api.jsStringLength (enforced, warn 600000, limit 1000000): warn threshold exceeded 1 time(s),
2max actual was 600010, current location: request/site Sites-SiteGenesis-Site/top pipeline
3Product-Show/interaction node/template refapp.default_.CustomDisplay

The message contains details to help identify problems. See:

• If a quota is enforced or not enforced
• If applicable, the warn threshold
• The limit
• The number of times since the last log entry for this quota that the warn threshold or limit was exceeded
• The highest observed reading (max actual)
• The current location, which shows where the warn threshold or limit was exceeded

j

Announcements

Choose Your B2C Commerce Storefront Type

B2C Commerce

Quick Start

Overview of B2C Commerce

Get Set Up

Build Your Site

Customize and Extend

Follow Best Practices

Test and Launch

Monitor and Maintain

Log Files

Log Center

Control Center

Configure Alerts

Maintenance Pages

Track Analytics

B2C Commerce Intelligence JDBC Driver

SCAPI

Storefront Next

Composable Storefront

Storefront Reference Architecture (SFRA)

Commerce Apps ISV Developer Guide

B2C Commerce Solutions

B2C Commerce Release Notes

B2C Commerce Reference Information

Ask the Community