You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any plan to later support websockets protocol (in addition to just http)?
I've been trying to see more trace data on one of my servlets, but since websockets is a different protocol altogether, and the data flow is usually server-to-client (instead of the traditional client-to-server requests), I've been largely unsuccessful.
I tried calling "stagemonitor.init()" and adding the "@Traced" annotations, and I'm now able to see the method names in the metrics tab. However, I don't see any numbers on any of them aside from the "All" row. Is there any way to just see what methods get invoked in a class and possibly trace it (regardless of protocol)?
The text was updated successfully, but these errors were encountered:
And regarding the call tree in the browser plugin, I see methods being invoked - but only those initiated by http requests. I was, however, able to see them through kibana as that seems to catch all methods being invoked regardless of what initiated the call tree (i.e. the parent level call wasn't an http web request - but rather an independent thread). So that's all working now.
Is there any plan to later support websockets protocol (in addition to just http)?
I've been trying to see more trace data on one of my servlets, but since websockets is a different protocol altogether, and the data flow is usually server-to-client (instead of the traditional client-to-server requests), I've been largely unsuccessful.
I tried calling "stagemonitor.init()" and adding the "@Traced" annotations, and I'm now able to see the method names in the metrics tab. However, I don't see any numbers on any of them aside from the "All" row. Is there any way to just see what methods get invoked in a class and possibly trace it (regardless of protocol)?
The text was updated successfully, but these errors were encountered: