Skip to main content
ngrok’s Traffic Inspector works with AI Gateway endpoints, allowing you to view full request and response bodies for debugging.

Enabling traffic inspection

Traffic Inspector is controlled at the account level:
1

Open 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
This is useful for:
  • 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

Traffic Inspector shows standard HTTP request/response data. The AI Gateway does not currently add AI-specific instrumentation to Traffic Inspector.Not currently available:
  • Which provider was selected from your configured list
  • Retry attempts and failover decisions
  • Token counts and cost estimates
  • Model selection strategy evaluation results
  • Per-provider latency breakdowns
  • API key selection details
These features are on our roadmap. Email [email protected] to tell us what you’d like to see—your feedback directly influences our roadmap.

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
Consider:
  • 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:
PlanRetention
Free3 days
Personal7 days
Pro30 days
Enterprise90 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

  1. Send a request to your AI Gateway endpoint
  2. Open Traffic Inspector
  3. Find your request by timestamp or endpoint
  4. 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