Salesforce Commerce Cloud is a scalable, cloud-based software-as-a-service (SaaS) ecommerce platform. This integration allows you to collect data from Salesforce Commerce Cloud and send it to your Logz.io account.

The default configuration uses a Docker container with environment variables.

Pull the Docker image of the Logz.io Salesforce Commerce Cloud data fetcher
docker pull logzio/sfcc-logs-fetcher:latest
Run the Docker container
docker run -d -e LOGZIO_SHIPPING_TOKEN=<logzio_shipping_token>
-e LOGZIO_LISTENER_URL=<logzio_listener_url> \
-e SFCC_SERVER_NAME=<your_sfcc_host> \
-e SFCC_CLIENT_ID=<your_sfcc_client_id> \
-e SFCC_LOG_SOURCE=operational
-e SFCC_CLIENT_SECRET=<your_sfcc_client_secret> \
logzio/sfcc-logs-fetcher:latest
Parameter Description Required/Default
<<LOG-SHIPPING-TOKEN>> Your Logz.io account token. Replace <<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to. Required
<<LOGZIO_LISTENER_URL>> Use the listener URL specific to the region where your Logz.io account is hosted. Click to look up your listener URL. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071. Required
SFCC_SERVER_NAME SFFC Server name from where you would like to collect logs. Required
SFCC_CLIENT_ID Client id related to the account that you need to send logs from. Learn more Required
SFCC_LOG_SOURCE Flag to represent which log types you would like to collect. operational for operational logs, security for security logs, all for both of them. Required
SFCC_CLIENT_SECRET Client secret related to the account that you need to send logs from. Learn more Required
Check Logz.io for your logs

Give your logs some time to get from your system to ours, and then open Kibana.

If you still don’t see your logs, see log shipping troubleshooting.

The default configuration uses a Docker container with environment variables defined by a configuration file.

Create a local directory for this integration

You will need a dedicated directory to use it as mounted directory for the Docker container of the Logz.io Salesforce Commerce Cloud.

mkdir sfcc-logs-fetcher
cd sfcc-logs-fetcher
Create a configuration file

In the directory created in the previous step, create a file variables.env as follows:

# Environment file for Logz.io Logs for SalesForce Commerce Cloud
LOGZIO_SHIPPING_TOKEN=<<LOG-SHIPPING-TOKEN>>
SFCC_SERVER_NAME=<<your_sfcc_host>>
SFCC_CLIENT_ID=<<your_sfcc_client_id>>
SFCC_CLIENT_SECRET=<<your_sfcc_client_secret>>
CCTAIL_ARGS=sfcc
LOGZIO_LISTENER_URL=https://listener.logz.io:8071

Replace the variable values as per the table below:

Parameter Description Required/Default
LOGZIO_SHIPPING_TOKEN <<LOG-SHIPPING-TOKEN>> Your Logz.io account token. Replace <<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to. Required
LOGZIO_LISTENER_URL Use the listener URL specific to the region where your Logz.io account is hosted. Click to look up your listener URL. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071. Required
SFCC_SERVER_NAME SFFC Server name from where you would like to collect logs (ex. dev01-mysandbox.demandware.net) Required
SFCC_CLIENT_ID Client id related to the account that you need to send logs from. Learn more Required
SFCC_CLIENT_SECRET Client secret related to the account that you need to send logs from. Learn more Required
Run the Docker container with the configuration file 2
docker run -d --env-file=variables.env logzio/webdav-fetcher:latest
Check Logz.io for your logs

Give your logs some time to get from your system to ours, and then open Kibana. You can filter for data of type cloud_commerce to see the incoming Salesforce Commerce Cloud logs.

If you still don’t see your logs, see log shipping troubleshooting.