Socket.IO Debugging
Debug Socket.IO connections, including the Engine.IO transport layer, namespaces, rooms, and event-based messaging.
Creating a Socket.IO session
- Navigate to Realtime in the dashboard
- Click New Session
- Select Socket.IO as the protocol
- Enter the server URL (e.g.,
https://my-app.com) - Optionally configure:
- Namespace — the Socket.IO namespace to connect to (default:
/) - Auth parameters — authentication data sent during the handshake
- Transport — force
pollingorwebsocket(default: auto-upgrade)
- Namespace — the Socket.IO namespace to connect to (default:
- Click Connect
Inspecting events
The dashboard displays Socket.IO events in real time:
Event stream
- Event name — the Socket.IO event name (e.g.,
message,chat:new, custom events) - Direction — emitted (outgoing) or received (incoming)
- Data — the event payload
- Timestamp — when the event occurred
- Acknowledgment — whether the event expects an ack callback
Engine.IO details
View the underlying Engine.IO transport:
- Transport type — polling or WebSocket
- Upgrade events — when the connection upgrades from polling to WebSocket
- Ping/pong — heartbeat messages
Sending events
Emit custom events from the dashboard:
- Enter the event name
- Enter the payload (JSON)
- Click Emit
Use cases
- Debug Socket.IO servers — inspect events without writing client code
- Namespace testing — verify namespace-specific event routing
- Auth debugging — test authentication handshakes
- Transport issues — diagnose polling-to-WebSocket upgrade failures