Content-capture libraries
Content-capture libraries allow you to capture, serialize, and mask request/response and header content directly within your service code.
This ensures that when a recording is captured we can pre-correlate unsampled data across your entire stack: from frontend screens and user actions, to backend traces, logs and request/response content and headers across all your system components.
Quickstart overview
To get started copy/paste this command in your terminal:
npm install -g @multiplayer-app/cli && multiplayer
Follow the steps in the guided setup wizard. The debugging agent CLI wizard will automatically install the right Session Recorder packages (e.g. @multiplayer-app/session-recorder-react, -node) so it can actually capture session data to debug against.
More information in the Multiplayer quickstart.
Manual setup
If you're manually setting up the content-capture libraries, please note the following:
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.
Content-capture libraries vs Multiplayer proxy
You have 2 options for routing your request/response content and headers data to Multiplayer:
-
Content-capture libraries.[YOU'RE VIEWING THIS OPTION ‼️] 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. See this guide.
You did it! What’s next?
🚀 If you’re ready to trial Multiplayer with your own app, you can follow the steps in the quickstart.
If you have any questions or trouble with the configuration, contact us.