DX Application Performance Management

  • Private Community

  • 1.  WebMethods payload inspection via CA APM Introscope

    Posted Oct 24, 2018 04:31 PM

    Has anyone used CA APM/Introscope to inspect the payload from WebMethods agents?

    My customers running WebMethods would like to know whether Introscope could “inspect” data and/or even “react” to it as it was being monitored (in this case monitoring WebMethods). At the time, wM still hadn’t upgraded to version 10 and the idea basically went on the back burner. Well, it’s come back around with the following specifics. Do you know if Introsope could be configured to monitor the “load” in either of the following scenarios? Scenario 1: (most difficult for Introscope but probably no code changes needed by us) In Introscope: MyObject.saveXML(String XMLinput) Inside the XML input is an element, let’s call it <StoreNumber></StoreNumber>. Is there any way to monitor the load on SaveXML *per* unique StoreNumber value? Obviously Introscope would have to parse out the StoreNumber element or call a method on MyObject that would return it. The ask would then be that Introscope monitor load on “saveXML-<StoreNumber>” as though it was a unique method. Scenario 2: If Scenario 1 is not possible, what about if MyObject contained a method that took “String storeNum” as a parameter? Such as … In Introscope: MyObject.saveStoreNumber(String storeNum) Would that allow us to monitor load of saveStoreNumber() per unique value of storeNum ? We had CA professional services come onsite and write some custom tracers to monitor WebMethods for us. Thanks. Chuck.



  • 2.  Re: WebMethods payload inspection via CA APM Introscope

    Broadcom Employee
    Posted Oct 24, 2018 04:47 PM

    Does someone have suggestions for Chuck? 



  • 3.  Re: WebMethods payload inspection via CA APM Introscope

    Broadcom Employee
    Posted Oct 25, 2018 01:15 PM

    Chuck, what you're asking for is possible in principle with a custom tracer, but could potentially incur a lot of overhead, especially your first option. Depending on the size and structure of the XML, having an Introscope tracer retrieve it and then parse it to extract the StoreNumber value might have more of a time, CPU or memory impact than you'd like.

    The second option seems more palatable, although I'm not sure if you're talking about instrumenting saveStoreNumber() with a tracer or having a tracer call saveStoreNumber().

     

    How about a third option: would it be possible for your developers to add the StoreNumber as a parameter e.g. if this is a servlet, as an HTTP header or cookie? I think a custom tracer could retrieve that pretty efficiently, and then a name formatter should allow you to have metrics separated by StoreNumber.