monitoring-alerting-commerce

Instrument commerce checkout observability with Prometheus alert rules and OpenTelemetry metrics.

14|3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/tomtoto757/ecomm-ai-skills-hub --skill monitoring-alerting-commerce-tomtoto757
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-alerting-commerce
Source: https://github.com/tomtoto757/ecomm-ai-skills-hub/tree/main/skills/platform-integrations-infrastructure/finsilabs/infrastructure-performance/monitoring-alerting-commerce
Command: npx skills add https://github.com/tomtoto757/ecomm-ai-skills-hub --skill monitoring-alerting-commerce-tomtoto757

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lack of commerce-specific observability leaves teams blind to revenue-impacting failures; this Skill provides the instrumentation, dashboards, and alerting guidance needed to detect checkout drops, payment failures, and cart errors before they hit sales reports.

Core Features & Use Cases

  • Commerce-domain metrics: checkout funnel counters, payment success/failure breakdowns by gateway and decline_code, and order creation latency histograms.
  • Platform guidance: recipes for Shopify, WooCommerce, BigCommerce and custom/headless storefronts including GA4, session recording, and synthetic checks.
  • Instrumentation & queries: OpenTelemetry initialization patterns, example metric names and histogram boundaries, PromQL queries for payment success rate and P99 latency, and Prometheus alerting rules with runbooks.
  • SLO & alert design: symptom-based alerts, non-zero for: durations, decline_code monitoring, and recommendations for prod vs staging routing and alert fatigue reduction.

Quick Start

Install OpenTelemetry on your storefront, import the provided Grafana queries and Prometheus rules, and enable the payment success and checkout availability alerts to begin monitoring revenue-impacting failures.

Frequently Asked Questions about monitoring-alerting-commerce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor payment success rate with Prometheus and PromQL?

To monitor payment success rate, this Skill provides specific PromQL queries and metric definitions that calculate the ratio of successful transactions to total attempts. It includes example metric names and histogram boundaries for OpenTelemetry instrumentation to track gateway performance.

What is the best way to alert on checkout funnel drops in Shopify or WooCommerce?

The best way to alert on checkout funnel drops is by applying symptom-based Prometheus alert rules with non-zero for durations. This Skill provides platform-specific guidance for Shopify, WooCommerce, BigCommerce, and custom storefronts to detect revenue-impacting failures.

Does this payment monitoring approach work with OpenTelemetry on headless storefronts?

This payment monitoring approach works with OpenTelemetry on headless storefronts by providing initialization patterns and custom metric instrumentation for checkout observability. It supports custom storefronts alongside hosted platforms to track P99 order creation latency.

How do I set up SLO burn-rate alerts for commerce health monitoring?

Setting up SLO burn-rate alerts involves configuring Prometheus alert rules with runbook annotations and applying recommendations for routing alerts to prod versus staging environments. This Skill outlines SLO burn-rate considerations to reduce alert fatigue while monitoring decline codes.

How do I track decline codes and payment failures in Grafana?

Tracking decline codes and payment failures in Grafana uses provided dashboard queries that break down payment success and failure metrics by gateway and decline code. This allows teams to visualize commerce health and identify specific revenue-impacting failures before they hit sales reports.