You’re on call.
What’s happening
A live incident is assigned when you start.
Your lab is being prepared.
Preparing your lab…
You were paged for failed customer checkouts.
Find the cause, restore checkouts, then ask the customer to try again.
WHEN YOU THINK IT’S FIXED
| Time | Event |
|---|
No events
Direction → observation → diagnostics. Open only what you need.
No hint is opened automatically. Your terminal, notes and investigation stay right where you left them.
Checking this session’s XP rules…
BEACON / DELIVERY PROBE
FIXED TEST EVENT · TEXT/PLAIN
deployment heartbeat
Send one event through the agent to Beacon. A correlated acknowledgement confirms the collector wrote it to its log.
One probe, not a recovery verdict. Use the dashboard and verify event delivery when you’re ready.
Send a heartbeat to inspect the delivery path. Results appear here only after a real request.
Follow this ID in the agent and collector logs.
OPENTELEMETRY / REQUEST PATH
Submit a fresh order and inspect the spans collected from its actual service path. Compare request meaning, timing and the durable result.
Test an order, then follow its trace across services.
Test an order to load its trace, or enter a trace ID from this session.
Spans can arrive after the response. Missing spans do not prove that work never ran. Trace observations support diagnosis; Verify checks the actual request path and stored order.
NAME SERVICE / APPLICATION LOOKUP
FRESH PUBLICATIONS · NORMAL DNS
Resolve a published service name through the normal application path and verify the service's correlated response.
One successful lookup is not sustained recovery. New service names continue to appear during verification.
Compare application access with resolver and authoritative answers.
SITE NETWORK / DESK REQUEST
ONE REQUEST · AFFECTED DESK
Compare the failing desk with a working one, hop by hop.
ARTIFACTS / PUBLICATION + READBACK
FRESH BYTES · RETAINED DATA
Publish a fresh artifact, read its bytes back, and check that active work and retained generations remain intact.
One publication is not sustained recovery. Compare with filesystem observations before verifying your fix.
Compare the publication result with filesystem observations and the dashboard.
EDGE / CUSTOMER OPERATIONS
DOCUMENTS + UPLOAD READBACK
Request documents through both customer hostnames, then upload fresh bytes and read them back. A successful status alone does not prove the correct result.
One operation set, not a recovery verdict. Compare with the dashboard before verifying your fix.
Compare the customer result with proxy configuration and the dashboard.
PORTAL / DOCUMENT ACCESS
TWO CLIENT COHORTS
Request a document through fresh HTTPS connections. Each client verifies the server identity, trust chain and document contents.
One probe, not a recovery verdict. Compare with the dashboard before verifying your fix.
Test the customer path, then compare its receipt with your terminal observations and dashboard.
1 / IN THE GUEST SHELL
2 / INSIDE THE DATABASE CLIENT
Compare with Docs. Keep observations in your scratchpad; hints are optional.
A probe verifies one operation. Full recovery also checks sustained success and reference data.
Use the database client to investigate, then test the application path here.
Follow this ID in the application logs.
THE EVERYDAY SERIES
A place for observations, loose ends, and the next good question.
$18.00 USD
THE CUSTOMER
Your cart is empty.
Checks live inventory through your lab. No payment is taken.
Search this ID in the service logs to follow the request.
This network blocks live terminals (often a corporate proxy). Try another network or hotspot.
SETUP STOPPED
Loading review…
Time ran out.
Lab cleanup is continuing in the background.