DocsEnterpriseSession replay and storage
EnterpriseEnterprise

Session replay and storage

Understand how the enterprise replay plugin exposes config and chunk ingestion, and what storage settings it expects.

Source of truthserver/engine/ee/replay/plugin.gosdk/sankofa_flutter/lib/src/replay/sankofa_replay.dart

Replay routes

The replay plugin exposes:

  • POST /api/ee/replay/chunk
  • GET /api/ee/replay/config
  • viewer routes under /api/ee/replay/...

Storage model

Replay chunk metadata is written to ClickHouse. Binary replay data is uploaded to B2-compatible object storage through the plugin's S3 client setup.

Required storage settings

The replay plugin expects storage configuration such as:

  • B2_ENDPOINT
  • B2_KEY_ID
  • B2_APP_KEY
  • B2_BUCKET_NAME

If those values are missing, replay uploads will fail even if the rest of the engine is running normally.