Term

When replay data is received from QM Capture, where does it go?

Definition

Replay data is sent to the ingestion services - (Neutron/Nuke) - which store the data as appropriate replay files on disk before an ETL process moves them into Google Cloud Storage (GCS) for long-term access.

Term

explain how the capture of data and replay works

Definition

When the QM script "records" a session, it doesn't send a video; it sends the "ingredients" to rebuild the page. This data hits the ingestion server, gets saved as a file, and is then tucked away in Google’s cloud storage. When a user clicks "Play" in the QM dashboard, the platform pulls these files from the cloud to reconstruct the session.

Term

capture data - lego example

Definition

Think of Replay Data like a Lego set. Instead of taking a photo of a finished Lego castle (a video), QM sends the instruction manual and the bricks to a warehouse (GCS). When you want to see the castle later, QM grabs the box from the warehouse and rebuilds it right in front of you.