Interested in our other Smart Alerts? Check out the catalogs for our other products:
⏮ Back to Proactive Services: Monitoring Overview
The Signature Success Plan comes with Proactive Services and Smart Alerts that will notify you in real-time when your custom Salesforce solution has inefficiencies, application performance degradations, or errors.
Here's a list of the current Smart Alerts available through Proactive Services, including their technical descriptions, business impacts, and the insights you will get from each one.
Note: Parenthesis within alert names means that it’s the number of individual smart alerts supported within the alert category
Ex: Critical Integrated Service (1-4) Performance means maximum 4 individual alerts for critical integrated services
| Category | Name | Technical Description | Business Impacts |
|---|---|---|---|
| Limit | Daily Log Volume Limit | Salesforce will monitor for LogCenter capacity limit reached. | Exceeding the maximum daily message limit in LogCenter means that LogCenter will no longer index error messages until the following day. This could negatively impact the ability to investigate issues |
| Error | Error Rate: Anomaly Detection | Salesforce will monitor error rates and exceptions to identify deviations from the normal and expected range. | An increase or change in error rates could be indicative of an implementation issue and cause a poor Customer experience on the site. Excessive writing to error logs can also result in limit issues and impede investigations. |
| Error | Error Rate: Increase in HTTP 400 errors | Salesforce will monitor for an increase in HTTP error code 400 - Bad Request | The Http 400 errors are usually due to malformed request, which leads to certain requests not being processed succesfully, leading to degraded user experience. |
| Error | Error Rate: Increase in HTTP 403 errors | Salesforce will monitor for an increase in HTTP error code 403 - Forbidden Error | The 403 (Forbidden) status code indicates that the server understood the request but refuses to authorize it. If authentication credentials were provided in the request, the server considers them insufficient to grant access. The 403 response belongs to the 4xx range of HTTP responses: Client errors |
| Error | Error Rate: Increase in HTTP 5xx errors | Salesforce will monitor increase in HTTP error codes 500 - 505:
| This HTTP 5xx status codes indicates that the server is aware that it is on error or is incapable of performing the request leading to requests not being processed successfully, resulting to degraded user experience. |
| Error | OCAPI: Error Rate Anomaly Detection | Salesforce will monitor OCAPI error rates and exceptions to identify deviations from the normal and expected range. | Degradations in OCAPI requests can impact the Customer experience, especially on mobile or when the solution is part of an externally hosted application framework |
| Error |
Critical Integrated Service (1-12) Errors | To ensure performance and availability of critical or revenue impacting third party services that might impact storefront experience, Salesforce monitors errors related to Third Party endpoint(s) calls. | Storefront users may face incomplete or degraded user experiences when those user flows involve errors related to third-party services (Cybersource, Avalera, Adyen, Paypal, Vertex, etc). |
| Performance | Application Request Rate - Drop | Salesforce will monitor request and session rates and warn of a potential impact to platform availability. | A drop in the application request rate implies that the site could also be loading slowly or potentially has become unavailable. |
| Performance | Average Application Response Time | Salesforce will monitor the application's aggregate average response time and identify periods when there are deviations from normal/expected response times. | Storefront and Business Manager visitors may experience a degraded user experience, including slow page response times or difficulty placing orders. |
| Performance | Order Failure Increase: Anomaly Detection | Salesforce will monitor order fail count to identify deviations from normal order rate/behavior. | An increase in Order Failure rate can be revenue impacting could be due to a disruption in order functionality or the unavailability of dependent services to successfully process the request. |
| Performance |
Order Processing Delay: Anomaly Detection |
Salesforce will monitor order processing rates to identify if orders are stuck in the "Created" stage and not moved to the next stage. | Delays in order processing can occur for any number of reasons. If left unchecked, this can lead to a large queue of orders and increases the potential for lost orders. |
| Performance | Order Rate Decrease: Anomaly Detection | Salesforce will monitor order rates to identify negative deviations from normal order rates. | Salesforce will monitor order rates to identify negative deviations from normal order rates. |
| Performance | System Workload: Anomaly Detection | Salesforce will monitor for significant increase in usage or deviations from normal/expected system resource utilization patterns. | High or sustained system workload usage can impact overall solution performance leading to degraded site visitor experiences. It can also impact site availability altogether. |
| Performance | Critical Integrated Service (1-12) Performance | To ensure performance and availability of critical or revenue impacting third party services that might impact storefront experience, Salesforce monitors availability and increase in average response times of Third Party endpoint(s) calls. | Storefront users may face incomplete or degraded user experiences when those user flows involve third-party services (Cybersource, Avalera, Adyen, Paypal, Vertex, etc). |
| Performance | Key Entry Point (1-5) Page Response Time | Salesforce will monitor average response times of key application entry points/API to identify deviation from expected/normal behavior. Some key entry points include; search, home, product, cart, content etc. | Storefront visitors may experience a degraded user experience including slow page response times or degraded site functionality. |
| Performance |
OCAPI: Critical Transaction (1-4) Average Response Time | Salesforce will monitor the aggregate average request response time of OCAPI requests to identify deviations from expected/normal response times. | Degradations in OCAPI requests can impact end user experience, especially on mobile or when the solution is part of an externally hosted application framework. |
| Category | Name | Technical Description | Business Impacts |
|---|---|---|---|
| Error | SCAPI: Increase in 5xx errors | Salesforce will monitor increase in HTTP 5xx errors for the SCAPI Shopper, Data and Custom APIs, and identify any deviations from the normal error rates. | An increase in 5xx error rate could be indicative of a server side issue and cause a poor customer experience on the storefront/application |
| Error |
SLAS: Increase in HTTP 5xx errors | Salesforce will monitor increase in HTTP 5xx errors for the following SLAS API endpoints, and identify any deviations from the normal error rates. | An increase in 5xx error rate could be indicative of a server side issue and cause a poor customer experience on the storefront/application. |
| Performance | Managed Runtime Availability | Salesforce will monitor for impact to the Composable Storefront Origin availability. | The Composable Storefront for B2C Commerce origin is the endpoint in Managed Runtime that will affect the availability of the Storefront(s). If the origin is unavailable, users won't be able to access the storefront. |
| Performance | SCAPI: Latency Alert | Salesforce will monitor the response times/latency of the SCAPI Shopper, Data and Custom APIs, and identify any deviations from the normal/expected response times/latency. | Degradations in SCAPI requests can impact the Customer experience, especially when the solution is part of an externally hosted application framework |
| Performance | SLAS: Latency Alert | Salesforce will monitor the response times/latency of the SLAS APIs and identify any deviations from the normal/expected response times/latency. | Degradations in SLAS API requests can impact the Customer experience, especially when the solution is part of an externally hosted application framework |
Salesforce may change the Proactive Monitoring, Smart Alert Catalog from time to time in its sole discretion. SFDC will provide customers with advanced notice of any planned downtime.
000392833

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.