Getting Started With Alerting
1. Product Overview & Introduction
What is Alerting
Alerting is a real-time monitoring system for payment performance metrics.
It helps you detect anomalies or performance issues as soon as they occur, giving you visibility and control over your most critical payment KPIs.
It provides:
- Slack notifications when a performance issue is detected
- A dedicated Dashboard page to explore and understand alerts in context
- Full self-serve capabilities to create and manage your own monitors
Key Use Cases
Alerting helps you monitor key indicators of payment health:
- Latency: Track Payment Provider HTTP latency (95th percentile) to detect downtimes
- Error Rate: Track Payment Provider related internal errors to detect technical issues (
gateway.internal-error,gateway.unknown-error,gateway.timeout,gateway.upstream-error) - Conversion Rate: Detect performance drops to protect your revenue
2. Monitor Types & Capabilities
Monitor Types
Alerting currently supports static threshold monitors, which trigger when a metric exceeds or falls below a defined threshold.
Static Threshold Monitors
Each monitor is defined by a set of configuration parameters:
| Parameter | Description |
|---|---|
| Metric | The metric being tracked (Conversion rate, Payment provider latency or Payment provider error rate) |
| Condition | The comparison operator used to trigger the alert (>, <) |
| Threshold | Numeric value that triggers an alert |
| Evaluation period | Time interval between two evaluations (default: every 5 minutes) |
| Recovery periods | The number of periods for an alert to be recovered (default: 1) |
| Filters | Optional filters to focus on specific data (gateway, currency, transaction metadata, etc.) |
| Minimum volume | Minimum volume required to trigger an alert (default: 100) |
Example Use Case
- Monitor name: Conversion Rate - Global
- Metric:
Conversion rate - Threshold: < 90%
- Recovery periods: 1
- Evaluation period: 5 minutes
- Minimum volume: 100
Purpose: Detect when overall conversion rate drops below 90% over a 5-minute window.
Monitor Configuration and Exploration
You can now create, edit, and delete your own monitors directly from the ProcessOut Dashboard:
- Adjust thresholds and sensitivity levels
- Define the metrics and filters that matter to you
- Manage notification settings independently
3. Notifications & Actions
Notification Types
- Slack: Alerts are delivered to your designated Slack channel, including:
- The metric and monitor concerned
- The observed value and threshold
- Direct link to the Alerting dashboard for detailed context
Deep Dive & Contextual Exploration
From any alert from the dashboard, you can access detailed data views:
- Jump to Analytics to analyze trends and segment impact
- Jump to Transactions to investigate affected payments in detail
4. Getting Started
-
Access the Alerting Tab
Go to Alerting tab in your ProcessOut Dashboard to view existing monitors. -
Create Your First Monitor
- Click Create Monitor
- Choose a Slack channel in the ProcessOut Workspace to receive alerts (contact ProcessOut Team if you don't have any)
- Select a metric
- Configure threshold, filters and volume settings
-
Investigate Alerts
- Use the Alerting dashboard to see open and past alerts
- Click an alert to access Analytics or Transactions for detailed investigation
5. Example Configurations
| Use Case | Metric | Filters | Threshold |
|---|---|---|---|
| PSP downtime detection | Latency | gateway=adyen | > 10s |
| Regional anomaly | Conversion rate | country=FR | < 50% |
| PSP technical issue detection | Error Rate | gateway=checkoutcom | > 5% |
Disclaimer
Alerting is the first version of our fully merchant-configurable alerting system.
We are actively improving it to make monitoring more accurate, flexible, and actionable.
Your feedback is essential — please reach out through your ProcessOut contact or via the support portal to share your experience or suggestions.
Updated about 2 hours ago
