Loading
Salesforce now sends email only from verified domains. Read More
Get Started with B2C Commerce
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Set Up Log Streaming to Third-Party Monitoring Tools

            You are here:

            1. Salesforce Help
            2. Docs
            3. B2C Commerce for Merchandisers and Administrators

            Set Up Log Streaming to Third-Party Monitoring Tools

            For enterprise-scale monitoring and automation, stream logs from B2C Commerce to third-party analytics platforms, including Splunk, Datadog, Grafana Loki, New Relic, Dynatrace, SumoLogic, and AWS Elastic Cloud. You can also use generic HTTP connections to stream logs to other tools.

            1. Log in to Log Center.
            2. Select the Log Streaming tab.
              Log streaming page in Log Center
            3. Create a new log stream configuration by clicking Plus button next to Log Streaming Configurations.
              New log stream configuration
            4. Enter the log stream name. You can use alphanumeric and special characters with spaces. You can’t use the same name for multiple configurations.
            5. Select a destination type. The options include Datadog, Dynatrace, Elastic Cloud on AWS, Generic HTTP, Grafana Loki, New Relic, Splunk (cloud and enterprise), and SumoLogic.
            6. Enter the third-party endpoint URL as the destination for the log.
              Destination Type ENDPOINT URL
              Splunk

              Splunk Cloud: https://http-inputs-firehose-<your_unique_cloud_hostname>.splunkcloud.com

              Splunk Enterprise: See Splunk Add-on for Amazon Kinesis Firehose
              Datadog

              US1: https://aws-kinesis-http-intake.logs.datadoghq.com/v1/input

              US3: https://aws-kinesis-http-intake.logs.us3.datadoghq.com/api/v2/logs?dd-protocol=aws-kinesis-firehose

              US5: https://aws-kinesis-http-intake.logs.us5.datadoghq.com/api/v2/logs?dd-protocol=aws-kinesis-firehose

              AP1: https://aws-kinesis-http-intake.logs.ap1.datadoghq.com/api/v2/logs?dd-protocol=aws-kinesis-firehose

              EU: https://aws-kinesis-http-intake.logs.datadoghq.eu/v1/input

              GOV: https://aws-kinesis-http-intake.logs.ddog-gov.com/v1/input
              New Relic

              US: https://aws-api.newrelic.com/firehose/v1

              EU: https://aws-api.eu.newrelic.com/firehose/v1
              Grafana Loki https://aws-logs-prod.grafana.net/aws-logs/api/v1/push
              Dynatrace https://live.dynatrace.com/api/v2/logs/ingest/aws_firehose
              SumoLogic

              https://sumologic.com/receiver/v1/kinesis/

              https://sumologic.net/receiver/v1/kinesis/
              AWS Elastic Cloud https://es.aws.elastic-cloud.com
              Generic HTTP Any HTTPS endpoint that can receive delivery from Firehose, per specification.
            7. If you selected Grafana Loki for the destination, enter a user ID.
            8. Enter the API token for the third-party tool.
              Destination Type API Token Documentation Reference
              Splunk Authentication Token Splunk Add-on for Amazon Kinesis Firehose
              Datadog Authentication Keys Datadog API and Application Keys
              New Relic API Keys New Relic API Keys
              Grafana Loki Token Grafana Labs: Configure Logs with Firehose
              Dynatrace API Token Stream logs via Amazon Data Firehose
              SumoLogic Any Sumo Logic: AWS Kinesis Firehose for Logs Source
              AWS Elastic Cloud API Key Elastic: Monitor Amazon Web Services (AWS) with Amazon Data Firehose
              Generic HTTP Customized Authentication Not applicable.
            9. Select a realm, and then configure the number of streams.
              For each realm, you can configure up to 5 streams per destination type.
            10. (Optional) For Edit Permission List, enter a comma-separated list of email IDs for the users who have edit access. There’s no limit to the number of email IDs that you can enter. Note these guidelines.
              • The user who configures the log stream is the primary owner.
              • The primary owner can enable, edit, and delete permissions for other users assigned to the same realm.
              • Invalid or incorrect email addresses are ignored.
              • Users assigned to the same realm can view the realm but don’t have edit or delete permissions.
            11. (Optional) Set filters. Next to Filters, click Plus button.
              Enter the filter field values exactly as shown in the table, or the parameters are ignored.
              • Use the OR operator for multiple values of a single filter type.
              • Use the AND operator for multiple filter types.
              • You can’t configure filters and negative filters for the same type.
              • Each row represents one filter type. If you configure multiple rows with the same type, they’re combined.
              Types Description Example
              Category Logs category type from search aggregation. Enter a comma-separated list of values.
              • Category Type
              • system
              • custom
              • customfiles
              • Jdbc
              • syslog
              • api
              • job
              • staging
              • sysevent
              • analytics
              • quota
              • deprecation
              • impex
              • batch
              • migration
              Request Logs request type from search aggregation. Enter a comma-separated list of values.
              • Request Type
              • JOB
              • BUSINESSMGR
              • STOREFRONT
              • TEMPORARY
              • REST
              Service Logs service type from search aggregation. Enter a comma-separated list of values.
              • Service Type
              • ecom
              • JWA
              • MRT
              Severity Logs severity from search aggregation. Enter a comma-separated list of values.
              • Severity
              • info
              • warn
              • error
              • debug
              • fatal
              Tenant Name Logs tenant name ID from search aggregation. Enter a comma-separated list of values.
              • Tenant Name
              • production.functional09.qa222 bgzz_prd
              • dev02.functional09.qa222 bgzz_s02
              • dev04.functional09.qa222 bgzz_s04
              Tenant Type Logs tenant type from search aggregation. Enter a comma-separated list of values.
              • Tenant Type
              • sbx
              • prd
              • stg
              • dev
            12. (Optional) Set negative filters. Next to Negative Filters, click Plus button.
              • Use the OR operator for multiple values of a single filter type.
              • Use the OR operator for multiple filter types.
              • You can’t configure filters and negative filters for the same type.
              • Each row represents one filter type. If you configure multiple rows with the same type, they’re combined.
            13. (Optional) Set parameters. Next to Parameters, click Plus button.
              Use parameters to customize any extra HTTP header, which ends up as an X-Amz-Firehose-Common-Attributes header. For more information, see Amazon Data Firehouse request and response specifications..
              • Grafana Loki parses HTTP header key with the prefix lbl_ into tags.
              • Datadog parses HTTP header keys into tags.
              • New Relic parses HTTP header key into attributes.
              • Splunk and Dynatrace don’t support parameters
              • Sumo Logic accepts _sourceCategory and _sourceName attributes for filtering.
              • AWS Elastic Cloud accepts the parameters es_datastream_name, include_cw_extracted_fields, and . For more information see Monitor Amazon Web Services (AWS) with Amazon Data Firehose.
              • Duplicate parameters aren’t combined.
            14. Save your configuration changes.
            15. Click Close.
            16. After you configure log your streaming, click Refresh, and check for any error messages.
             
            Loading
            Salesforce Help | Article