Multiplayer OpenTelemetry Collector
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.
The most efficient way to do this is by leveraging OpenTelemetry, an industry standard for collecting telemetry data.
If your services don't already use OpenTelemetry, you'll first need to install the OpenTelemetry libraries.
Once your services are instrumented with OpenTelemetry follow the steps below.
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.
-
OpenTelemetry Collector. 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.
‼️ For a full overview of the Multiplayer OpenTelemetry Collector check this GitHub readme: multiplayer-otlp-collector ‼️
Setup prerequisites
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 and follow STEP 1 of the configuration step.
- Generate your API key.
ℹ️ In case you already generated an API key in STEP 1 (with the “JavaScript Client Library” or “CLI Apps” options) you can re-use that, and skip generating a separate API key for the backend.