Skip to main content

Multiplayer Proxy

ℹ️ GitHub repo for reference: multiplayer-proxy ℹ️

Multiplayer is a full stack session recorder that captures everything you need to develop new features, fix bugs, and work with AI coding tools. Multiplayer collects front-end screens, user actions, backend traces, metrics, logs and full request/response content and headers - all auto-correlated in a single session.

Options overview​

To fully unlock the potential of full stack session recording, you need to connect your backend to Multiplayer, sending your application’s telemetry data (traces, logs, request/response and header information) to our platform.

In addition to sending traces and logs, we recommend that you capture request and response content to enrich your full stack session recordings.

We offer two solutions for this:

  • In-service code capture libraries. Capture, serialize, and mask request/response and header content directly within your service code. This is an easy way to get started, especially for new projects, as it requires no extra components in your platform.

  • Multiplayer Proxy. This option allows you to handle capturing this data outside of your services and it’s ideal for large-scale applications. It supports all languages, including those like Java that don't allow for in-service request/response hooks. The proxy can be deployed in various ways, such as an Ingress Proxy, a Sidecar Proxy, or an Embedded Proxy, to best fit your architecture.

‼️ This guide only covers the Multiplayer Proxy. ‼️

Setup porerequisites​

To correctly configure the Multiplayer proxy make sure to:

Multiplayer Proxy setup​

‼️ Follow the steps in this GitHub readme to set up: multiplayer-proxy ‼️

You did it! What’s next?​

You’ve successfully configured the Multiplayer in-service code capture , congratulations! 🎉

To leverage the Multiplayer full stack session recordings at their fullest, make sure to:

If you have any questions or trouble with the configuration, contact us.