Fix NGINX Propagation

Explore RUM in Splunk

5 minutes

In this step, you’ll observe how RUM sessions appear add context to requests and how they appear in Splunk Observability Cloud. This is the “problem state” of how the APM issue reflects in RUM.

The RUM Request Path

Note

Allow 2–5 minutes after deploy for RUM data to appear..
  1. Navigate yo the app in the browser http://localhost:30080
  2. Refresh the browser session using Command + Shift + R
  3. Open browser DevTools → Network tab
  4. Place an order
  5. In the Network tab, inspect a POST /api/orders request
  6. Confirm the request includes a traceparent header (injected by Splunk RUM)

Example header:

text 
traceparent: 00-2476afefb1c010fa965d0e96d09c76c4-03d3d28b2b0f6290-01

nginx-trcprnt

Note

Copy the traceID value (highlighted in blue) - we will use this in the next step.

The browser appears to be correcly instrumented and processing requests as expected.

Observe in Splunk RUM

  1. Navigate to Digital Experience → Session Search
  2. Filter Environment → workshop-$INSTANCE
  3. Open a recent session
  4. Locate fetch requests
  5. You will see an APM correlation link for ‘api/catalog`.
  6. Hover over the hyperlink to view correlated trace details

rumtrc

Last Modified ·