Content-capture Libraries
Multiplayer is a full stack session recorder that captures everything from front-end screens, user actions, backend traces, metrics, logs, to 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/response and header content to enrich your full stack session recordings.
We offer 2 solutions for this:
-
Content-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.
‼️ This guide only covers the content-capture libraries. ‼️
Setup prerequisites
To correctly configure the Multiplayer content-capture make sure to
- Login into your Multiplayer account. If you don't already have one, create a free trial at go.multiplayer.app
- Complete the Client setup in STEP 1 of the configuration steps
- Route traces and logs to Multiplayer using one of these 2 options:
Supported languages
- Node.js
- Python
- Java - Java only supports capturing request/response and header content with the proxy.
- .NET
- Go
- Ruby
- 🚧 PHP
- 🚧 Rust
- 🚧 Swift
- 🚧 Generic
ℹ ️ Java doesn’t allow for in-service request/response hooks. However, you can use the Multiplayer proxy instead, which can be deployed in various ways, such as an Ingress Proxy, a Sidecar Proxy, or an Embedded Proxy, to best fit your architecture.
You did it! What’s next?
You’ve successfully configured the Multiplayer content-capture library, 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.