Find more info about sockjs request


I’m seeing a crash on Prod and I want to uncover more information about how it happened.
I don’t have much on the stacktrace and I want to see what route/page on the app was accessed right before the crash.

I went to NGINX access logs during the timestamp of the crash and see things like,

"GET /sockjs/038/50hdshx2/websocket HTTP/1.1" 101 788550 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36" "IP"

Is there anyway I can use the /sockjs/038/50hdshx2/websocket part to deduce what route was hit? Or even get a subscription Id?


Why not use an APM to get more details when something fails?

1 Like

Good point, I’d played with Monti briefly and will have to look into it again.

Does using an APM introduce a non-trivial amount of overhead and/or latency?

The overhead, if any, is so negligible to the performance and fixed issues that you will gain by using it.

1 Like

Sounds good, is there one for Meteor that you recommend. Seems MontiAPM is what community prefers. I’d had good results with NewRelic on an Express app, but I’m not sure how that’ll play with Meteor.

MontiAPM is great and will give lots of details about your app

1 Like