E2E Correlation
In this final step, you’ll confirm that traces flow continuously from browser click through the NGINX gateway, API services, RabbitMQ, and the background worker - all visible as a single trace in Splunk Observability Cloud.
End-to-End Validation #
Send New Web Request #
bash
curl -s -X POST http://localhost:30080/api/purchases \
-H "Content-Type: application/json" \
-d '{"productId":"mount-eq6-pro","quantity":1,"customerEmail":"final-test@cosmic.shop"}' \
| python3 -m json.tooljson
{
"message": "Order accepted for fulfillment",
"order": {
"orderId": "ORD-1719763200456",
"productName": "SkyWatcher EQ6-R Pro Mount",
"total": 1899.0
},
"traceHint": {
"traceId": "4bf92f3577b34da6a3ce929d0e0e4736",
"spanId": "..."
}
}Task
Copy the trace ID (the 32-character hex segment) - you’ll use it to search in Splunk APM.
Note
Wait 2 seconds for the fulfillment worker to process the RabbitMQ message.
bash
kubectl -n cosmic-shop logs deployment/fulfillment-worker --tail=3text
Fulfilled order ORD-1719763200456 (payment PAY-1719763200456) for SkyWatcher EQ6-R Pro Mount