> ## Documentation Index
> Fetch the complete documentation index at: https://ngrok.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Traffic Observability Overview

> Learn about ngrok's traffic observability features for inspecting requests, debugging issues, and exporting events to external logging systems.

Troubleshoot and monitor traffic flowing through your endpoints to understand what was sent, received, and how it behaved.
Inspect requests and responses in real time with Traffic Inspector, or export traffic events to your own tools for retention, analysis, and alerting.

## Features

* [Traffic Inspector](/obs/traffic-inspection/) - Real-time view of HTTP traffic with request replay capabilities.
* [Event exporting](/obs/events/) - Subscribe to log sources and publish events to external destinations.

## Use cases

<Columns cols={2}>
  <Card title="Verify endpoint pooling" icon="check-circle" href="/gateway/load-balancing-multiple-clouds/">
    Use Traffic Inspector to verify that load balancing works correctly by checking which agent IPs respond to requests.
  </Card>

  <Card title="Monitor API gateway traffic" icon="chart-line" href="/guides/api-gateway/monitor-ngrok/">
    View and replay requests with Traffic Inspector, then export logs to Datadog for monitoring dashboards and alerts.
  </Card>

  <Card title="Add custom event logging" icon="file-text" href="/traffic-policy/examples/event-logging/">
    Use the log action in Traffic Policy to capture custom metadata for unsuccessful requests and export to your logging system.
  </Card>

  <Card title="Log requests with metadata" icon="database" href="/traffic-policy/actions/log/">
    Add structured logging to your traffic policies with custom metadata fields using CEL expressions for dynamic values.
  </Card>
</Columns>

## What's next?

* Get started with [Traffic Inspector](/obs/traffic-inspection/) to view and debug your traffic in real-time.
* Learn how to [export events](/obs/events/) to external logging systems.
* Browse the [event reference](/obs/events/reference/) to see all available log sources.