Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Websocket support #117

Closed
dignifiedquire opened this issue Feb 16, 2014 · 6 comments
Closed

Websocket support #117

dignifiedquire opened this issue Feb 16, 2014 · 6 comments

Comments

@dignifiedquire
Copy link

I wanted to ask if there are any plans to support websockets, especially primus and sockjs. Nearly all our node based servers do some kind of socket based communication and without support for websockets this agent becomes nearly useless :(

@maziyarpanahi
Copy link

I would like to have that kind of support for those products and also Socket.io as so many people have been using it for a long time. It is a good suggestion, I second it.

@othiym23
Copy link
Contributor

Hi! This is a very commonly requested feature, so you're not alone. Websockets, being session-based, presume a very different performance model than transactional HTTP requests. As such, New Relic is likely to roll out support for websockets in many tiny little pieces -- number of sockets opened / closed over time, event throughput, etc -- before we tackle big features like session traces or integrating websockets with real user monitoring (RUM) or cross-application tracing.

Readers of this issue: your best bet, if you want websocket / long-polling / WebRTC data channel support for Node, is to contact [email protected] and to be as specific as possible about what performance problems you encounter with those technologies that you'd like New Relic to help you resolve. Adding a 👍 to this issue will not be helpful.Your detailed feedback, on the other hand, will help our product team figure out how to prioritize the various pieces of work here, and will help them make a case for bumping this work up the priority queue. Thanks!

@dignifiedquire
Copy link
Author

@othiym23 Thanks a lot for the info. I might start taking matters into my own hands as I haven't found any solution that does provide that and the newrelic agent seems a good starting point. Any pointers where to look/to begin?

@othiym23
Copy link
Contributor

@dignifiedquire most of the most useful changes will probably require changes to how New Relic conceptualizes performance data, but that's the part that will take a while. You might take a look at our plugin platform and custom dashboards if you want to start exploring options. Good luck!

@Zolmeister
Copy link

👍

@txase
Copy link

txase commented Aug 12, 2014

Hi folks,

As an update, we are close to releasing custom instrumentation! This will allow you to mark when transactions start and end, including websocket transactions. Look for it in a coming release.

At the same time, we are closing down support through github issues. For future issues or feature requests, please follow up with us at http://support.newrelic.com. We are better able to support you through our dedicated portal than through github issues.

Thanks!

@txase txase closed this as completed Aug 12, 2014
@newrelic newrelic locked and limited conversation to collaborators Aug 12, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants