Investigating and debugging ecommerce errors often requires technical teams to switch between client-side and server-side tools to connect the dots. Noibu’s Logs Integration bridges this gap by integrating server-side logs for errors, warnings, and fatal events from your ecommerce platform into session replays. Additional filtering and search capabilities in Noibu make it easy for teams to discover trends and analyze log details. This enables a single, streamlined workflow to resolve customer-impacting errors.
Note: this feature is currently in beta. Beta features are still in development as we test and evaluate. They may have limited functionality and can change without notice. |
Configuring Logs Integration
At this time, Logs Integration is only available for the Salesforce Commerce Cloud (SFCC) clients using the SG or SFRA architecture. To configure the SFCC logs integration, you must (1) request access through your Noibu CSM; (2) pass the SFCC Session ID as a custom attribute to Noibu, and (3) enable log streaming within SFCC. Learn more about enabling the SFCC logs integration.
Viewing Session Replays with Log Data
During playback of a session replay that includes logs data, any relevant error, warning, or fatal log events will be displayed in the session timeline.
Clicking the “i” icon next to the log will open a new tab with full session and log details. This provides a comprehensive view of server-side data from your ecommerce platform, which can shed additional light on how to debug and resolve an issue that impacted customers.
For example, if Noibu shows the user experiencing a client-side “payment failed” error on your site, logs ingested from your ecommerce platform may indicate the payment gateway API failed. With this integrated insight, teams can confirm the customer-impacting issue was caused by a back-end problem with the payment gateway, not a client-side input problem.
Filtering Sessions with Logs
When log integration is enabled, you can filter the sessions page by specific log types (error, warning, or fatal). In combination with other filters (e.g. browser type, OS, or URL), this can help you find and review user sessions specifically associated with server-side problems.
In addition to logs, if the session contains additional custom attributes (e.g. order ID), you can also filter to those specific sessions.
Clicking on any row in the table will open a panel where the session replay can be reviewed in detail. Learn more about Session Replay.
Analyzing the Logs Index
The Logs page in Noibu gives you a real-time running list of warning, error, and fatal logs from your ecommerce platform provider over a period of time. When the logs integration is enabled, you will see every log that is ingested here. This page also allows you to identify anomalous spikes in error logs, and review any associated session replays to determine if and how the event impacted a user.
Filtering Logs
The Logs page allows you to adjust the time period under review, from the last hour, day, 7 days, 14 days, 30 days, or a custom range. Choosing Custom will bring up a date picker, allowing you to specify the date and time range.
You can also choose a custom date range by clicking and dragging on the Logs chart.
Noibu collects logs with Error, Warning, and Fatal severity levels. You can toggle the different types of logs on or off as needed.
Additionally, you can filter logs to specific SFCC session IDs. This allows you to see all logs associated with a specific session.
Use the search field to narrow the search for specific logs by looking for text within a log message, using quotation marks to search for an exact term or phrase.
Logs Chart and Index
The chart and the data beneath it will refresh automatically as you adjust your search filters. Hovering over a point on the chart will show you how many of each log type occurred at that time.
Click the Share button to copy a link to the Logs page with current filters applied, or to copy the chart to your clipboard. This can be a useful way to loop in other teams for investigation, or to share visual confirmation that a fix has been applied and log event frequency has decreased.
Beneath the chart is a detailed list of logs for the time period selected, presented in reverse chronological order. For each item in this table you will see the severity level (warning, error, or fatal), a preview of the log message, the time the event occurred, and a link to the impacted session replay (if available).
Clicking on any row in this table will bring up a side panel with full details about the log event.
If available, the log details will also include a link to the relevant session replay. However, although logs are ingested in real-time, session replays are not processed until the user’s session has been completed. This means that in many cases, a user’s session will still be active at the time a log appears in the table. Recent logs will display a "session pending" icon until the associated session replay has finished processing.
To specifically find user sessions with associated logs, consider filtering the sessions page instead.
Learn more about configuring Logs Integration for Salesforce Commerce Cloud (SFCC).