DX Application Performance Management

Expand all | Collapse all

Re: APM issues with Non-Oracle JVMs

Jump to Best Answer
  • 1.  Re: APM issues with Non-Oracle JVMs

    Posted 09-14-2016 10:51 AM

    So one last thing. The whole purpose for this effor is because I wanted to monitor a specific class.

    I constructed this PBD to monitor said class:

     

    ########################################################################

    # PBD Class/Methods

    # v3

    # 7SEP2016

    ########################################################################

     

    #Class and Events

    SetFlag: CESearch

    TurnOn: CESearch

    IdentifyClassAs: com.blah.cpp.classevent.controller.SearchController CESearch

    TraceAllMethodsIfFlagged: CESearch BlamePointTracer "Class_and_Events_Search|{classname}|{method}"

     

    I was expecting this to show up under the frontend. But, at the time the frontend folder didn’t exist.
    Also, can someone tell me if I wrote this correctly and where in the Investigator tree I should expect to see this?

     

    Thank you.

    -George



  • 2.  Re: APM issues with Non-Oracle JVMs

    Posted 09-14-2016 11:23 AM

    Making this a new branch



  • 3.  Re: APM issues with Non-Oracle JVMs

    Posted 09-14-2016 11:49 AM

    Okay. Thank you.



  • 4.  Re: APM issues with Non-Oracle JVMs
    Best Answer

    Posted 09-14-2016 12:36 PM

    Never mind I got this to work correctly.

     

     

    Thanks all.



  • 5.  Re: APM issues with Non-Oracle JVMs

    Posted 09-14-2016 12:43 PM

    Hi George:

      What did you do to get it to work?

    Thanks

    Hal German



  • 6.  Re: APM issues with Non-Oracle JVMs

    Posted 09-14-2016 12:55 PM

    Under the:

    TraceAllMethodsIfFlagged: CESearch BlamePointTracer "Class_and_Events_Search|{classname}|{method}"

     

    The last part "Class_and_Events_Search|{classname}|{method}"  defines the tree architecture. so I can't just simply do "Class_and Events_Search" with out adding the sub-tree {classname}. And I would think you would need to add {method} as well, if are using the TraceAllMethodsIfFlagged.

     

    Otherwise the tree looks really weird