đź“„ Initiative Spec: INT-30 Product Monitoring & Ops Dashboard
Status: 🔵 Active (Definition Stage) Owner: azmi Strategic Intent: Guarantee platform reliability and merchant trust through real-time observability of critical funnels.
1. The “Why” (Strategic Context)
- The Problem: We currently rely on reactive feedback (merchant complaints) for system failures. A single minute of downtime or checkout failure directly destroys GMV and merchant trust.
- The Goal: Move to a Proactive Ops model where the team is notified of an issue before the merchant notices.
- Target Metric: Mean Time to Detect (MTTD) < 5 minutes for critical errors.
2. The “What” (Solution Components)
2.1 Critical Product Funnels (The Heartbeat)
- Checkout Success Rate: Real-time monitoring of successful vs. failed 1-click checkout attempts.
- QR Payment Health:
- Generation Latency: Time taken to generate a dynamic QRIS code.
- Scan-to-Pay Conversion: Monitoring for high drop-offs between “Scan” and “Payment Success”.
- Recollection Bypass Detection: Alerting when an MCA merchant’s daily QR volume drops significantly below their historical baseline (e.g., >50% drop vs 7-day average), indicating potential revenue diversion.
- Core API Availability: Uptime monitoring for the primary transaction engine.
2.2 Notification & Dashboarding
- Slack Ops Channel: Real-time alerts for “Critical Failures” (e.g., 5 consecutive checkout errors).
- Internal Ops Dashboard: A centralized screen in the office/internal portal showing:
- Current Live GMV (hourly).
- Checkout Success Rate (last 24h).
- System Health Status (Red/Green).
3. Implementation Phases
Phase 1: Critical Slack Alerts
- Checkout Error Webhook: Trigger Slack notification when checkout error rate exceeds 5% in a 10-minute window.
- Availability Heartbeat: Simple monitor to check if the main site/API is responding.
Phase 2: Internal Ops Dashboard
- Metric Aggregation: Building the data pipeline to show hourly GMV and conversion rates.
- Merchant Health View: A dashboard showing which merchants are seeing higher-than-average abandonment rates.
4. Key Metrics (ROI)
- Uptime: 99.9% for core checkout flows.
- Time to Resolve: Reduced via immediate Slack alerting.
5. Action Items
- Define the “Critical Thresholds” for Slack alerts (e.g., 500 errors = P1).
- Connect internal logs to a Slack Webhook.
- Draft the UI/UX for the Internal Ops Dashboard.