You are here:
Log Center Alerts in B2C Commerce
Monitor custom alerts across all Log Center data sources from a centralized interface. Configure notifications to identify application performance degradations before they affect your users. Route alerts in real time via email, Slack, and PagerDuty to help your teams respond to critical system events.
- Log Center Alert Types in B2C Commerce
To determine the best method for monitoring your environment, review the available alert types in this table. - Create a Log Center Alert
Monitor conditions and send notifications. Catch behavioral anomalies early, get notified when a log delivery pipeline fails, or create an alert for a specific incident. - Create a Slack Channel for Log Center Alerts
To keep your teams aligned during incidents, set up Slack notifications in B2C Commerce. - Create a PagerDuty Channel for Log Center Alerts
For on-call escalation and incident management, set up PagerDuty notifications in B2C Commerce. When you route Log Center notifications in B2C Commerce to PagerDuty, the alert's state lifecycle is mapped to a specific PagerDuty action and severity. Each alert monitor uses a unique deduplication key, so repeated triggers update the existing open incident instead of creating duplicate incidents. - How Notification Channels Respond to Alert States
How a notification channel in B2C Commerce responds to an alert is based on the alert state. An anomaly detection alert fires once when an anomaly is detected and doesn’t track whether a condition persists or is cleared. - Access Control for Log Center Alerts
Verify that your role allows alert creation and management. - Troubleshoot Log Center Alerts
If you’re missing Log Center notifications in B2C Commerce, check these likely causes and fixes.
Did this article solve your issue?
Let us know so we can improve!
