Enabling traffic inspection
Traffic Inspector is controlled at the account level:1
Open Dashboard Settings
Go to ngrok Dashboard Settings
2
Enable Full Capture Mode
Under Observability, enable Full Capture Mode
3
View Traffic
Access the Traffic Inspector to see captured requests
What you can see
With Traffic Inspector enabled, you can view:- Full request bodies (prompts, messages, parameters)
- Full response bodies (completions, usage data)
- Request and response headers
- HTTP timing information
- Status codes
- Debugging prompt issues - See exactly what was sent to the provider
- Verifying responses - Confirm the model returned expected output
- Testing configurations - Verify your AI Gateway setup is working correctly
- Troubleshooting errors - See error responses from providers
Current limitations
Best practices
Disable in production
Full Capture Mode stores complete request and response bodies, which may include:- User prompts containing sensitive information
- PII in conversation context
- API responses with confidential data
- Disabling Full Capture Mode in production environments
- Enabling temporarily only when debugging specific issues
- Using separate endpoints for development vs production
Data retention
Traffic Inspector data is retained based on your ngrok plan:| Plan | Retention |
|---|---|
| Free | 3 days |
| Personal | 7 days |
| Pro | 30 days |
| Enterprise | 90 days |
Filtering traffic
Use the Traffic Inspector’s filtering capabilities to find specific requests:- Filter by endpoint URL
- Filter by HTTP status code
- Filter by time range
- Search request/response content
Example: debugging a failed request
- Send a request to your AI Gateway endpoint
- Open Traffic Inspector
- Find your request by timestamp or endpoint
- Expand the request to see:
- The model and messages sent
- The provider’s response or error
- Response headers including rate limit information
Security considerations
Data visibility
When Full Capture Mode is enabled:- All team members with dashboard access can view request bodies
- This includes prompts, user messages, and AI responses
- Consider access controls for sensitive environments
Compliance
If your organization has compliance requirements (HIPAA, GDPR, etc.):- Review whether storing request/response bodies is permitted
- Consider using Traffic Inspector only in development
- Consult your compliance team before enabling in production
See also
- Traffic Inspection Documentation - Full ngrok Traffic Inspector docs
- Metrics Reference - Use metrics for intelligent routing
- Error Handling - Understanding retry behavior