Skip to main content

Platform Debugger

đź“Ś If you have any questions shoot us an email or join us on Discord! đź’ś

Platform Debugger​

The Multiplayer Platform Debugger is the only debugger built for the complexity of distributed systems.

It leverages OpenTelemetry to allow teams and users to create complete session recordings, capturing everything: frontend screens, backend traces, metrics, logs, and full request/response content and headers. No data is left behind.

It helps your team pinpoint and resolve bugs faster and save time combing through APM data.

Screenshot of Platform Debugger

Getting Started with Platform Debugger​

To set up the Platform Debugger follow these steps:

  • Open your project
  • In the left-side menu, click "System" to open the System Dashboard
  • Click "Configure Auto-Docs + Debugger"
  • Name your integration
  • Hit "Create"
  • An OpenTelemetry (OTel) token will be created for your OTel integration.
  • Follow these steps to configure OpenTelemetry

ℹ️ The Platform Debugger and System Auto-Documentation both leverage OpenTelemetry. That’s why they share a set up window.

Once you click “Confirm”, we will proceed with the Multiplayer OTel integration and start adding backend data (e.g. traces and logs) to your Platform Debugger sessions. Please note that if you close the set up window before finishing the set up, new OTel tokens will be generated when you re-open it.

Platform Debugger Main Functionalities​

These are the main functionalities in Platform Debugger:

  • Record sessions to see the exact steps to reproduce an issue.
  • See deep platform insights for each session: everything that happened in your backend platform - metrics, traces, and logs - not just front end APIs.
  • Review user issues: Enable your end-users to record deep session replays of any bugs / unexpected behaviours they come across.
  • Share insights with your team — skip the long tickets, emails and endless Slack threads.

Platform Debugger Top Navigation​

Screenshot of Platform Debugger top navigation bar

Left:

  • Views Panel: Create a list of filtered views within a session, by selecting specific session events you want to group together.

Center:

  • Session Information Panel: Open the session information panel to review and edit the session name, comments, browser details, etc.
  • Enter Fullscreen
  • Switch to List View: Move the insights panel to the bottom of the screen (switching from vertical to landscape view) for a better deep dive into events, console, traces, logs.
  • Hide the Recording: Hide the recording of the user steps.

Right:

  • [Coming soon] AI Assistant
  • [Coming soon] Share session: View-only sharing is coming soon. In the meantime, you can invite your team members to collaborate within your Multiplayer project and review all debugger sessions.

Review and edit session information​

Screenshot of Platform Debugger Session Information panel

The Session Information Panel has two tabs:

About - where you can:

  • Edit the session name
  • Add tags to a session (type the tag name and press enter)
  • Review any comments users included in the session recording
  • Review the recorder's information (name, browser info, etc.)
  • Delete a session

Comments - where you can leave comments for your team.

Create a custom view of events​

Screenshot of Platform Debugger custom views

To create a custom view of a selection of events within a debugging session follow these steps:

  • Open a session within the Platform Debugger
  • Open the "Views" panel
  • Select the events you want to group within a view
  • Click "Create a view" in the "Views" panel

Review information per session event​

Screenshot of Platform Debugger session events

For each session we capture backend traces, metrics, logs, and full request/response content and headers. No data is left behind!

To view the information for each event recorded, double click on the desired session event.

Filter session events​

Screenshot of Platform Debugger filtering events

Events within a Platform Debugger session can be filtered by:

  • Type (trace, log, event, console)
  • Starred events
  • Component
  • Level (info, error, warn, debug)

Screenshot of Platform Debugger filtering levels

Levels are assessed automatically. Here's an overview what each means:

  • INFO: Indicates a general informational messages about the application’s state and workflow. Used for key checkpoints and expected operations.
  • DEBUG: Indicates a detailed diagnostic information useful for developers when troubleshooting issues.
  • WARN: Indicates a potential issue that is not currently breaking the application but may cause problems in the future.
  • ERROR: Indicates a serious issue that could point to failures in execution, preventing normal operation.

Next Steps​

You did it! What’s next?