|
Re: Monitoring RAP application with New Relic [message #1752415 is a reply to message #1752383] |
Mon, 23 January 2017 15:25 |
|
I have NewRelic tracking a couple of RAP instances, but unfortunately the results are not particularly useful. It works for tracking down time and general performance problems, but as you mentioned you can't drill down into the details. This is because RAP is not a typical JavaEE web application and that is what NewRelic expects. The main problem is that RWTServlet.service doesn't actually do any of the work. RAP does all of the work on a single UIThread (to be SWT compatible), but the servlet request will come in on any of the servlet container's worker threads. RWTServlet tells the UIThread to wake up and process the request, but that all happens on the other thread.
That said, it should be possible to make NewRelic understand how RAP works using their custom metrics, but I haven't had the time to look into that myself. If you have a paid plan with NewRelic, I think they have some setup services that might be able to assist with that. You could also find someone in the RAP community willing to work as a consultant.
Hope that helps,
Cole Markham
[Updated on: Mon, 23 January 2017 19:03] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.03369 seconds