Liigu põhisisu juurde

Taasesitus

Seansi taasesitus salvestab, mida kasutaja ekraan tegelikult tegi: DOM-i muutused ja interaktsioonid, SDK poolt tükkidena püütud ja konsoolis tagasi vaadatud. Salvestamine on kliendi kohta valikuline, sisendid on vaikimisi maskitud.

At a glance

Enable
createWebClient({ sessionReplay: true, replayHost })
Intake
POST /v1/replay, chunked, project key
Read
replaySessions, replayChunks over GraphQL
Masking
Inputs masked by default, client-side
Auth
Project key to record, access token to watch
  • Tükkhaaval püüdmine: salvesti saab nummerdatud tükke, nii et poole seansi pealt suletud sakk jätab alles kõik seni saadetu.
  • Maskimine on kliendipoolne: maskitud sisu ei lahku kunagi brauserist, mitte ei peideta kuvamisel.
  • Taasesituslingid on meelega lühiealised; aegunud link väljastatakse uuesti laadimisel, mitte ei kuku vaikselt läbi.

Kuidas see töötab

The web SDK records DOM mutations and interactions, serialises them into numbered chunks and posts each chunk to the recorder with the project key, flushing on an interval and on page hide. The replay processor stores the chunks with their session metadata: whose session, how many events, whether masking was on. The console lists sessions and plays one back by fetching its chunks through short-lived links, in order, so a recording streams rather than downloading whole.

Kust seda leida

SurfaceOperation
RESTPOST /v1/replay (recorder intake, project key)
GraphQLreplaySessions, replayChunks queries
RealtimeNone: session lists read on demand
MCPNone

Näide

TypeScript
import { createWebClient } from '@prodantix/sdk/web';

const prodantix = createWebClient({
  apiKey: process.env.PRODANTIX_KEY,
  replayHost: 'eu.replay.prodantix.com',
  sessionReplay: true,
  // Inputs are masked by default; widen or narrow with sessionReplayOptions.mask.
});

Replay is a web SDK capability: recording needs a DOM, so the Dart and Python SDKs do not carry it. Watching back happens on the Replay screen.