icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

We are working on something new...

A Fresh New Splunkbase
We are designing a New Splunkbase to improve search and discoverability of apps. Check out our new and improved features like Categories and Collections. New Splunkbase is currently in preview mode, as it is under active development. We welcome you to navigate New Splunkbase and give us feedback.

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading Salesforce Commerce Cloud Add-on for Splunk
SHA256 checksum (salesforce-commerce-cloud-add-on-for-splunk_233.tgz) a93ac28a48c9606f436a7d4f9e662a54335a2a5b2b538ec5f260063d187bb473
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

splunk

Salesforce Commerce Cloud Add-on for Splunk

Overview
Details
Salesforce 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. The Salesforce Commerce Cloud Add-on for Splunk provides the ability to collect logs from B2C WebDAV locations.

TA-SFCC

Salesforce Commerce Cloud Add-on for Splunk




Description

The Salesforce Commerce Cloud Add-on for Splunk collects various log types from Salesforce Commerce Cloud (formerly Demandware).

Log Types
- Analytics Engine
- API Logs
- Console Logs
- Custom Debug Logs
- Custom Error Logs
- Custom Fatal Logs
- Custom Info Logs
- Custom Logs
- Custom Warn Logs
- Data Replication Logs
- DBInit SQL Logs
- Debug Logs
- Deprecation Logs
- Error Logs
- Fatal Logs
- Import Inventory Logs
- Import Pricebook Logs
- Info Logs
- Jobs Logs
- Migration Logs
- Performance Logs
- Quota Logs
- Security Logs
- Service Logs
- SQL Logs
- Staging Logs
- Sysevent Logs
- Syslog Logs
- Warn Logs


Platform and hardware requirements

This topic discusses the underlying requirements for the Salesforce Commerce Cloud Add-on for Splunk.


Hardware and Operating System requirements


The Splunk Supporting Add-on for Active Directory has memory, CPU, and disk requirements that meet standard hardware requirements for the core Splunk Enterprise platform. Deploy hardware that meets or exceeds these hardware requirements.

  • For additional details about Splunk Enterprise system requirements, see "System requirements" in the core Splunk Enterprise documentation.
  • For information about estimating hardware requirements for a Splunk deployment, see "Introduction to capacity planning for Splunk Enterprise" in the Capacity Planning Manual.


Operating system requirements


You can install the add-on on Splunk Enterprise instances that run a supported operating system. See the list of supported Windows and *nix operating systems.


What versions of Splunk Enterprise does the app support?

Salesforce Commerce Cloud Add-on for Splunk supports Splunk Enterprise versions 8.x (python3)




Distributed Installation

This table provides a quick reference for installing this app onto a distributed deployment of Splunk Enterprise.

Salesforce Commerce Cloud Add-on for Splunk

Splunk Instance Type Supported Required Comments
Search Heads Yes No
Indexers No No
Heavy Forwarders Yes Yes
Universal Forwarders No No




Setup and Initial Configuration


  • Configuration -> Add-on Settings

    • Ensure that the Local State Directory exists and is writable
  • Configuration -> Account -> Add

  • Choose a name for the account and enter the account Username and Password
  • Click Add
  • Under Inputs -> Create New Input, select the type of log to collect

    • SFCC OOTB Logs
    • Select the log type from the list
    • Name the input
    • Select a collection interval in seconds (i.e. 60)
    • Select the index to collect logs
    • Select the Account to use for authentication
    • Fill in the SFCC B2C Commerce instance name
    • Edit the log directory, if necessary
    • Edit the provided regular expression, if necessary (the default should work)
    • Select SSL certificate verification, if needed
    • Select "Set State Only?" to collect the current state information without forwarding or ingesting logs into Splunk
    • Click Add

    • Custom Logs

      • Choose "Custom Log"
      • Name the input
      • Select a collection interval in seconds (i.e. 60)
      • Select the index to collect logs
      • Select the Account to use for authentication
      • Fill in the SFCC B2C Commerce instance name
      • Edit the log directory, if necessary
      • Using the provided regular expression convention, fill out the log file pattern (i.e. ^custom-logname-.*)
      • Select SSL certificate verification, if needed
      • Select "Set State Only?" to collect the current state information without forwarding or ingesting logs into Splunk
      • Click Add


Inputs and Log Sources


Input Name Description
Analytics Engine B2C Commerce analytics
API Logs API Problems
Console Logs Internal console log entries
Custom Debug Logs Debug messages in custom jobs, imports, payment or code
Custom Error Logs Errors in custom jobs, imports, payment or code
Custom Fatal Logs Fatal errors in custom jobs, imports, payment or code
Custom Info Logs Informational logs in in custom jobs, imports, payment or code
Custom Logs Custom errors
Custom Warn Logs Warn messages in custom jobs, imports, payment or code
Data Replication Logs Data Replication Logs
DBInit SQL Logs SQL used during dbinit.
Debug Logs Debug information
Deprecation Logs Deprecated APIs
Error Logs Errors in B2C Commerce scripts, templates, code and other areas
Fatal Logs Fatal errors in B2C Commerce scripts, templates, code and other areas
Import Inventory Logs Inventory Import
Import Pricebook Logs Price Book Import
Info Logs Information logs reported on B2C Commerce scripts, templates, code and other areas
Jobs Logs Shows job status information
Migration Logs Internal migration data
Performance Logs Internal performance data
Quota Logs B2C Commerce quota details
Security Logs Security logs
Service Logs Service Logs
SQL Logs SQL replication issues
Staging Logs B2C Commerce data and code replication processes
Sysevent Logs Appserver registration and cartridge-related logs
Syslog Logs API processing, data staging, and error handling
Warn Logs Lock status reports, slot warnings and warnings for servlets

Release Notes

Version 2.3.3
Nov. 11, 2021
  • Fixed a race condition causing collisions in the state files [ISSUE-17]
0
Installs
17
Downloads
Share Subscribe LOGIN TO DOWNLOAD

Subscribe Share

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
Splunk, Splunk>,Turn Data Into Doing, Data-to-Everything, and D2E are trademarks or registered trademarks of Splunk Inc. in the United States and other countries. All other brand names,product names,or trademarks belong to their respective owners.