跳到主要内容
版本：最新版

Router Replay

Overview​

router_replay is a route-local plugin for overriding replay/debug capture on one route.

Key Advantages​

  • Lets one route override the router-wide replay default.
  • Supports request and response body controls.
  • Makes storage limits explicit instead of hidden.

What Problem Does It Solve?​

Replay capture is useful, but some routes need different capture policy than the router-wide default. router_replay lets one route opt out or override request/response body capture limits without changing global replay storage settings.

When to Use​

  • one route should override the router-wide replay policy
  • capture limits should be explicit per route
  • replay should be disabled for a specific route while staying on elsewhere

Configuration​

To disable replay for a route, add:

plugins:
  - type: router_replay
    configuration:
      enabled: false

To customize capture for a route, add:

plugins:
  - type: router_replay
    configuration:
      enabled: true
      max_records: 10000
      capture_request_body: true
      capture_response_body: true
      max_body_bytes: 4096
      max_tool_trace_steps: 100

Request bodies, response bodies, and tool traces can contain secrets or personal data. Capture the minimum needed, set retention in the shared replay service, and restrict replay read permissions. See a complete example: config/fragments/plugin/router-replay/debug.yaml.