The only tool you need to know what is happening and how to fix it.
Go alertingexception-trackerissue-trackinglogsmetricsmonitoringobservability-platformopen-telemetryotelsession-replaytelemetrytraces
Shoply demo runbook
The full setup lives in README.md (build, seed, traffic). This file is the tour to give once data is flowing.
Projects: Shoply Storefront (react — issues, sessions, replays) and Shoply API (opentelemetry — endpoints, traces, logs, metrics, AI, monitors).
Suggested tour
- Issues (backend) — open
assignment to entry in nil map: full Go stack from the recovered panic, occurrences over time, the owning endpointPOST /api/coupon, and the trace waterfall showing the SQL spans. - Distributed tracing — open a react issue like
Request to /coupon failed (500): the occurrence carries the distributed trace id and links straight to the backend trace. - Session replay — from the same react issue open the replay clip; then the Sessions page for full sessions with varied users, viewports and rage-scrolling window shoppers.
- Endpoints —
GET /api/productsp95 vs p50 (N+1 slow path),POST /api/checkoutlatency spread, all endpoints grouped by route (ids collapse into:id). - Logs — filter severity ERROR; every line links to its trace.
- Metrics & dashboards — Server/Application Metrics pages (
shop-backend), the OTelemetry Server Agent + Go Application dashboards, and Shoply Business (orders, revenue, coupon failures). - AI Traces — Conversations tab: the order-status conversation shows the
lookup_ordertool call; the refund complaint is flagged; Users tab has per-user costs. - Monitors — three green checks +
Payments Providerdown: incident, uptime bars, and the check_down page it opened (Pages sidebar badge). Ack it live. - On-call — team, weekly schedule, escalation policy;
/status/shoply-statuspublic page with the resolvedElevated checkout error rateincident timeline. - Post-mortem — the linked write-up under Monitors → Post-Mortems.