DX Application Performance Management

Expand all | Collapse all

Tracing IBM commerce REST API URLs

Jump to Best Answer
  • 1.  Tracing IBM commerce REST API URLs

    Posted 10-16-2015 11:38 AM

    Hi,

     

    We are monitoring iBM web sphere commerce application. By default, it is tracing the regular boundaries like ESP/JSP/Servlet/ECActionServlet etc. But the REST API interface in iBM commerce is not monitored(traced) as a single trace URL like a Servlet URI path. It is getting monitored as individual bean and framework calls. For e.g., if we invoke a URL /rest/store/cart, it creates three rows in the trace session and it is not knitting all the transactions together and recognizing the same as /rest/store/cart.

     

    IBM REST - https://www-304.ibm.com/support/docview.wss?uid=swg27039020&aid=1

     

    These requests go through several filters including the existing Servlet filters. The rest package names are given below. Has anyone monitored this successfully without creating individual trace rows for components belonging to the same REST call?

     

    IdentifyMatchingClassesAs: com.ibm.commerce.rest.* DiagTracing

    IdentifyMatchingClassesAs: org.apache.wink.server.internal.servlet.* DiagTracing

    TraceComplexMethodsIfFlagged: DiagTracing BlamePointTracer "Custom|Rest|{packageandclassname}|{method}"



  • 2.  Re: Tracing IBM commerce REST API URLs

    Posted 10-16-2015 11:38 AM

    Just to confirm.. We are running APM 10. This was the case with APM 9.X as well.



  • 3.  Re: Tracing IBM commerce REST API URLs
    Best Answer

    Posted 10-20-2015 06:43 PM

    Hi Selvakr,

     

    you need to deploy the JAX-RS field pack to be able to monitor the JAX-RS restful API. Please contact your CA team to get it.

     

    Ciao,

    Guenter



  • 4.  Re: Tracing IBM commerce REST API URLs

    Posted 10-27-2015 10:01 PM

    Thanks. We did work with our CA team to test the field pack. The way this field pack arranges the transactions by their handlers and the method types is amazing. Why can't we have this included in the supported version? I think the smart instrumentation should recognize regular backends like apache http clients, Http Url connection, LDAP queries etc out of the box. We did see the apache http client getting recognized automatically. But the same can be for the other two.