Skip to content
Supermetry

Configure session replay storage

Store replay blobs on local disk or S3-compatible storage and set per-site limits.

Choose where replay blobs are stored, then set retention and quota limits for each site.

  1. Enable replay for the instance in the Supermetry environment file.

    SUPERMETRY_REPLAY_ENABLED=true

    Restart Supermetry after changing it.

  2. For local storage, use the default $SUPERMETRY_DATA_DIR/replay, or set a directory explicitly.

    SUPERMETRY_REPLAY_DIR=/var/lib/supermetry/replay

    A systemd path must remain under /var/lib/supermetry unless you also extend the unit’s ReadWritePaths.

  3. For S3-compatible storage instead, set all required values together.

    SUPERMETRY_REPLAY_S3_ENDPOINT=https://s3.example.com
    SUPERMETRY_REPLAY_S3_BUCKET=supermetry-replays
    SUPERMETRY_REPLAY_S3_REGION=eu-central-1
    SUPERMETRY_REPLAY_S3_ACCESS_KEY=CHANGE_ME
    SUPERMETRY_REPLAY_S3_SECRET_KEY=CHANGE_ME
    SUPERMETRY_REPLAY_S3_PREFIX=production

    The prefix is optional. While a session is active, uploads collect under $SUPERMETRY_DATA_DIR/replay-spill.

  4. In Settings → Site settings → Session replay, enable replay for the project and set Retention (days) and Quota (bytes). The defaults are 30 days and 5 GB per site; environment values act as instance-wide ceilings.

    The hourly replay-retention job removes recordings older than the effective retention and then removes the oldest recordings when the quota is exceeded.

  5. Save the project settings and record a test session with the per-site installation snippet.

What you should see: Effective recording shows On, and new recordings appear without a storage error.

Section titled “Related”