Guide
See the requests that reach a tunnel
See the requests that reach a tunnel, who answered each one and how long it took.
- Applies to
- All plans; durable tunnels only
- Time
- About 5 minutes
- What it changes
- Reads request records. It does not change the tunnel.
- Last reviewed
- , by Product documentation
Before you begin
What to know before you start
- A request record is kept for 24 hours, and the newest 500 requests of each tunnel. Pinned requests are not trimmed by the count, but they also expire after 24 hours.
- Everyone who can see the tunnel in your workspace can read its inspector.
Steps
Step 1. Open the tunnel in the dashboard and choose Open request inspector.
You should see: A list shows requests, newest first.
Step 2. Send a request to the tunnel's address, then refresh the list.
You should see: A new row appears with the method, the path, the status and the duration.
To check: The list also refreshes itself while the page is open.
Step 3. Select a request to see its detail.
- The method and the path. Query values are replaced, so a token in the address is not stored.
- The status, and who answered: your app, or InstaWormhole itself with a code such as connector-unavailable or origin-failed.
- The size and type of the request and the response, and the first part of the sender's address, never the full address.
- The request and response headers, with sensitive values replaced by redacted.
You should see: You see the detail and can tell whether your app or the edge produced the answer.
Step 4. Narrow the list with the filters, and add a note or pin a request you want to keep in view.
You can filter by status class, method, path text and time. A note can be up to 500 characters.
You should see: The list shows only matching requests; a pinned request shows a pin.
You are done when
- You can find a request you sent and see its method, path, status and who answered.
What to do next
If something goes wrong
- The inspector is empty.
- Only durable tunnels are recorded. A quick address from the connector without --tunnel is not. Create a tunnel in the dashboard and connect with its command.
- A request you sent is missing.
- Requests that the password prompt refuses, and requests for an unknown address, are not recorded. The inspector records requests that passed the access check.
- A burst of requests shows fewer rows than you sent.
- A tunnel records at most 10 requests a second. Requests beyond that are counted as not recorded instead of slowing the tunnel.
Undo or clean up
- Delete one request or choose Delete all in the inspector.
Related
This page is part of Inspect and replay. Still stuck? Contact support.