Skip to main content

All data captured

Multiplayer session recordings are full stack by default. After following all the configuration steps you can expect the following data to automatically correlated per session.

Frontend data​

  • User clicks
  • Page navigations + loads
  • Session metadata
    • Browser information
    • OS information
    • Device type
    • Screen size
    • Pixel ratio
    • Cookies enabled/disabled state
    • Harware concurrency
    • Package version
  • DOM events
  • Console messages (message + stack trace)
  • Network requests
  • HTML source code

ℹ️ For a detailed overview guide, please refer to: How Multiplayer records and replays user interactions and data. Please note that Multiplayer is built with privacy in mind and, by default, all user inputs are masked.

Backend data​

  • Backend errors
  • Correlated distributed traces and logs per session, with no sampling
  • Request / response content per session, including from inside the system components (e.g. going from one service to another)
  • Header content per session, including from inside the system components (e.g. going from one service to another)

ℹ️ For a detailed overview guide, please refer to: How Multiplayer backend tracing works

🔑 Pro tip: Multiplayer is backend agnostic and supports OpenTelemetry: you can seamlessly integrated it with whichever observability stack you already use.

Additional context​

Next steps​

👀 If this is the first time you’ve heard about us, you may want to see full stack session recordings in action. You can do that in our free sandbox: sandbox.multiplayer.app

🚀 If you’re ready to trial Multiplayer with your own app, you can follow the Multiplayer configuration steps. You can start a free plan at any time: go.multiplayer.app

📌 If you have any questions shoot us an email or join us on Discord! 💜