Marketplace Production Alerts: Combine Failure Metrics, Logs, Request and Trace IDs

TL;DR: Page only when a pricing-rule cohort breaches its user-facing failure SLO in one region, then attach a correlation key that lets the responder move from the alert to logs and traces. Keep raw errors as investigation evidence, not separate pages. A polling worker can evaluate the rule every 30 seconds, but it needs bounded labels, delayed-data tolerance, and an explicit rollback gate. For a marketplace releasing a new pricing rule behind a flag, the useful question is not whether the application emitted an error. It is whether flagged quote requests in the EU or US are failing often enou