Using appmetrics-dash with existing socket.io connection

[Kristina-Ribacionkaite]

Passing server to monitor options results in Error during websocket handshake: Unexpected response code: 400. Without server option socket.io client and backend connects fine, but it creates new http server with default port 3001.
Is there a way to keep existing socket.io connection without creating a new server?
We are using node 6, express ^4 and socket.io and socket.io-client 1.7.3.

[tobespc]

@Kristina-Ribacionkaite How are you passing the server options ?

You should be able to just put the following in your code to use the existing server

var dash = require('appmetrics-dash');
dash.attach();

Make sure you add this before you require any servers

[Kristina-Ribacionkaite]

@tobespc we are using dash.monitor()

const appm = require('appmetrics');
const dash = require('appmetrics-dash');

dash.monitor({ server: ourAwesomeServer, appmetrics: appm });

Where ourAwesomeServer is our http server.

[tobespc]

@Kristina-Ribacionkaite ok, can you replace those three lines with these 2 please

var dash = require('appmetrics-dash');
dash.attach();

make sure your put those lines before you define your ourAwesomeServer

[noxxious]

Hi, the problem here is actually that appmetrics-dash will use the default socket.io listening path (/socket.io), which is wrong as most of the client applications due that. The proper way would be listen to a different (appmetrics-dash specific path). I've created the PR #136

[mrausch]

+1 for accepting PR #136
I have an application that already uses socket.io and I cannot use appmetrics-dash with that application.

[noxxious]

@mrausch, you still can, but your application has to be configured to use non-default socket.io path unfortunately.