Multiplayer OpenTelemetry collector
The Multiplayer OpenTelemetry collector allows you to connect your backend to Multiplayer, sending your application’s telemetry data (e.g. traces, logs) to our platform.
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 and logs.
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 Multiplayer OpenTelemetry collector, please note the following:
Prerequisites
If your services don't already use OpenTelemetry, you'll first need to install the OpenTelemetry libraries.
To correctly configure the Multiplayer OpenTelemetry Collector 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 step
- Generate your API key
- Follow the installation steps in the multiplayer-otlp-collector repo
Supported languages
Multiplayer exporter vs OpenTelemetry collector
You have 2 primary options for routing your backend data to Multiplayer:
-
Multiplayer exporter. This is a great choice for new applications or startups because it's simple to set up and doesn't require any additional infrastructure. You can configure our exporter to send all session recording data to Multiplayer while optionally sending a sampled subset of data to your existing observability platform. See this guide.
-
OpenTelemetry Collector. [YOU'RE VIEWING THIS OPTION ‼️] We recommend this option for large, scaled platforms, because it provides more flexibility by having your services send all telemetry to the collector, which then routes specific session recording data to Multiplayer, while routing other data to your existing observability tools.
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.