---
schema_version: "1"
id: 4c08926e4204ed4f6f53a9f527623f2f1350c72daed7220e8ff5a10751b80bb3
title: Log Streaming for Enhanced Monitoring
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_log_streaming_faq.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_log_streaming_faq.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c95829411e9db28ce2078e0f278637738b733d06aa355c01be7363530394d4db
description: Log Center supports log streaming to third-party monitoring and analytics tools. You can also stream logs using a generic HTTP connection. With these tools, Log Center users get enterprise-scale monitoring and automation capabilities. All B2C Commerce Log Center customers get log streaming at no additional cost.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Log Streaming for Enhanced Monitoring

Log Center supports log streaming to third-party monitoring and analytics tools. You can also stream logs using a generic HTTP connection. With these tools, Log Center users get enterprise-scale monitoring and automation capabilities. All B2C Commerce Log Center customers get log streaming at no additional cost.

Supported tools include:

- Splunk
- Datadoc
- New Relic
- Grafana Loki,
- Sumo Logic
- Dynatrace
- AWS Elastic Cloud

Review this information about log streaming, and then configure it.

## Log Streaming Operation

- Stream sandbox logs.
- To verify that logs have originated from Log Center, specify parameters when you configure log streaming. When you stream logs, these parameters can pass extra attributes as metadata to the third-party vendors. Most of these vendors can parse Firehose HTTP header X-Amz-Firehose-Common-Attributes, and can receive this metadata.
- To turn log streaming on and off, use the stop and play button.
    
    ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_important.png)
    
    Important If you disable and re-enable streaming, streaming resumes for only new logs. When log streaming is off, data for the time period is lost.

## Log Streaming Configuration Guidance

- If you configure log streaming multiple times for the same realm, the result can be duplicate logs. To avoid this situation, create separate log streaming configurations for production logs and non-production logs. Separate configurations make sure that logs get sent only one time, and helps you keep your data organized.
- After you configure a log stream, only new logs are streamed. Existing files aren’t in the log stream.

## Log Streaming Frequency and Performance

- Logs stream in batches. The time between each message can be from 20 seconds to two minutes, depending on how fast logs are cached and streamed.
- Log streaming is a real-time service. You can't configure logs to stream periodically, for example, every 5 minutes. You also can't stream logs from a specific number of days in the past.
- Log volume limits don't impact log streaming. Streaming continues.

## Log Streaming Support

- If you have integration problems with logs in a third-party tool, create a support ticket?
- If the API token used for log streaming expires, it is your responsibility to update it. We don’t automatically renew tokens.

## Third-Party Documentation for Log Streaming

Log streaming uses AWS Firehose as an underlying streaming service. For more information about AWS Firehose integration, see these resources.

- [New Relic](https://docs.newrelic.com/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose/)
- [Generic HTTP](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html)
- [Grafana Loki](https://grafana.com/docs/grafana-cloud/monitor-infrastructure/monitor-cloud-provider/aws/logs/firehose-logs/config-firehose-logs/)
- [Datadog](https://www.datadoghq.com/blog/stream-logs-with-firehose-and-datadog/)
- [Splunk](https://docs.splunk.com/Documentation/AddOns/released/Firehose/ConfigureFirehose)
- [Dynatrace](https://docs.dynatrace.com/docs/setup-and-configuration/amazon-web-services/integrate-with-aws/aws-logs-ingest/lma-stream-logs-with-firehose)
- [SumoLogic](https://help.sumologic.com/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-logs-source/)
- [AWS Elastic Cloud](https://www.elastic.co/docs/solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose)

- **[Set Up Log Streaming to Third-Party Monitoring Tools](https://help.salesforce.com/s/articleView?id=cc.b2c_set_up_log_streaming.htm&release=264.0.0&type=5)**  
    For enterprise-scale monitoring and automation, stream B2C Commerce logs to third-party analytics platforms, including Splunk, Datadog, Grafana Loki, New Relic, Dynatrace, SumoLogic, and AWS Elastic Cloud. You can also use a generic HTTP connection to stream logs to other tools.
- **[Set Log Streaming Notifications](https://help.salesforce.com/s/articleView?id=cc.b2c_set_log_streaming_notifications.htm&release=264.0.0&type=5)**  
    Create and update notifications for proactive monitoring of B2C Commerce log streaming.
- **[Security Logs Streaming](https://help.salesforce.com/s/articleView?id=cc.b2c_security_logs_streaming.htm&release=264.0.0&type=5)**  
    B2C Commerce security logs contain sensitive information such as login info, and client download info.