View HTTP Redirect Metrics
The Redirect tab shows a per-hop breakdown of timing metrics for each step in an HTTP
redirect chain, so you can identify which hop causes latency.
| Where Can I Use This? | What Do I Need? |
|---|
- Prisma Access (Managed by Strata Cloud Manager)
- Prisma Access (Managed by Panorama)
- Strata Cloud Manager
|
|
When a user accesses a SaaS application, the initial HTTP request often
triggers a chain of redirects through identity providers (IdPs), and gateways before
reaching the application. Without redirect visibility, the Experience Score reflects
only the first hop, making it impossible to identify which step in the chain is
causing poor performance.
ADEM redirect monitoring enables synthetic web tests to follow these
redirect chains and report per-hop timing data in a waterfall view.
The Redirects tab is available on the following pages:
Path Topology
A Redirect node appears in the Path Topology widget between the network path nodes
and the Application node when redirect data is available for the selected time
sample. The node displays the number of redirect hops (for example, "3 hops"). Hover
over the node to see the URLs for each hop. If no redirects are detected for the
selected time period, the Redirect node does not appear.
To view the Redirects node, scroll to the Path to
domain widget in the User Details Experience page:
Click the node to open the Redirects tab.
The Redirects tab displays seven summary cards at the top of the page:
| Card | Description |
|---|
| Total Redirect Time | Sum of Time to Last Byte (TTLB) values across all 3xx
hops. |
| Redirect Hops | Total number of 3xx redirect hops in the chain. |
| Total DNS Time | Aggregated DNS lookup time across all redirect hops. |
| Total TCP Time | Aggregated TCP connect time across all redirect hops. |
| Total SSL Time | Aggregated SSL handshake time (Time for the complete TLS
negotiation) across all redirect hops. |
| Total Server Processing Time | Aggregated server response time (time from request sent to first
response byte received) across all redirect hops. |
| Total Download Time | Aggregated time taken across all redirect hops to receive the
complete response body from the server after the first byte
arrives. |
The waterfall chart displays one row per hop in chronological order. Each row
shows:
- URL/Request: The full URL for the hop (truncated with a hover tooltip
showing the complete URL).
- Status: The HTTP status code for the hop (for example, 302).
- Server: Time for the server to respond (TTFB).
- Download: Time taken to receive the complete response body (TTLB).
- Duration: Hover over a bar segment to see the start time, end time, and
total hop time for that metric.
The waterfall also displays the following indicators:
- Loop Detected: If the agent detects a redirect loop (the same URL appears
twice in the chain), the row displays a Loop Detected icon.
- 10-hop limit warning: If the chain reaches 10 hops and the last hop
returns a 3xx status code, a warning banner appears: "10-hop limit reached.
Additional redirects may not have been captured."
