DX Application Performance Management

Expand all | Collapse all

CA APM ENTRY POINT DETECTION

Jump to Best Answer
  • 1.  CA APM ENTRY POINT DETECTION

    Posted 10-11-2018 03:25 AM
      |   view attached

    Hi

     

    I have set the value of introscope.agent.deep.entrypoint.enabled to True and all the settings that are provided on docops but I can't see the 

    Automatic Entry Points folder in the metric browser under the Agent stats.

     

    I have attached a picture of how the folder appears in the hierarchy.

     

    Regards 

    Imran



  • 2.  Re: CA APM ENTRY POINT DETECTION
    Best Answer

    Posted 10-11-2018 08:15 AM

    Dear Imran:

    You did not say your release . So I am going with APM 10.7

     

    https://docops.ca.com/ca-apm/10-7/en/troubleshooting/agent-troubleshooting/agent-does-not-automatically-detect-a-known-backend -- One possible issue 

    https://docops.ca.com/ca-apm/10-7/en/using/apm-webview/collect-and-analyze-transaction-traces 

    1) The agent saves entry points in the AutoPersist.pbd, which is persisted in the <Agent_Home>\core\config\hotdeploy directory.-- Was this created?

    2) Note: Ensure the introscope.autoprobe.dynamicinstrument.enabled property in the IntroscopeAgent.profile is set to true. This configuration allows the agent to report entry point metrics without requiring an application restart. --  Was this done?

    3) See https://docops.ca.com/ca-apm/10/en/implementing-agents/java-agent/configure-java-monitoring/configure-smart-instrumentation  --Verify Smart Instrumentation

     

    Failing that, please open a case, if no one responds



  • 3.  Re: CA APM ENTRY POINT DETECTION

    Posted 10-11-2018 08:28 AM

    Hi Hallett

     

    yes, my release is APM 10.7

    1. AutoPesist.pbd was not created

    2. yes introscope.autoprobe.dynamicinstrument.enabled property in the IntroscopeAgent.profile is set to true.

     

    But, Automatic Entry Points folder was not created



  • 4.  Re: CA APM ENTRY POINT DETECTION

    Posted 10-15-2018 03:19 AM

    Hi 

     

    Please update its urgent

     

    Regards  

    Imran



  • 5.  Re: CA APM ENTRY POINT DETECTION

    Posted 10-15-2018 10:06 AM

    Dear Community:

       Can you offer assistance as well?

     

    Dear Imran:

       See 

    https://docops.ca.com/ca-apm/10/en/implementing-agents/java-agent/configure-java-monitoring/configure-smart-instrumentation 

    Verify Smart Instrumentation

     

    Failing that, please open a case, if no one responds

    Thanks 

    Hal German



  • 6.  Re: CA APM ENTRY POINT DETECTION

    Posted 10-15-2018 06:38 PM

    Hi Imran Ali Khan,

    You confirmed in related thread (Duplicate Post) AutoPersist.pbd file doesnt exist that:

    - All Smart Instrumentation settings are enabled

    - AutoPersist.lock file is created in the hotdeploy directory to eliminate a permissions problem

     

    I would therefore suggest you follow Hal's advice to create a support case: 

    https://comm.support.ca.com/csupport/CaseManagement/cases/new

     

    Thanks

     

    Lynn



  • 7.  Re: CA APM ENTRY POINT DETECTION

    Posted 10-15-2018 08:12 PM

    Hi Imran Ali Khan,

    It maybe you don't have socket activity to generate the entry points in AutoPersist.pbd

    Have you tried the Verify Smart Instrumentation steps suggested by Hal?

    Configure Smart Instrumentation - CA Application Performance Management - 10.0 - CA Technologies Documentation 

     

    Also if you enable DEBUG in agent profile you should see more information e.g. below is from an example I have for socket activity:

     

    Hope it helps

     

    Regards,

     

    Lynn

    ===

    10/16/18 05:14:36 AM IST [DEBUG] [IntroscopeAgent.Agent] getting bytes for class -org.teiid.net.socket.SocketServerConnection
    10/16/18 05:14:36 AM IST [DEBUG] [IntroscopeAgent.Agent] searching for path -org/teiid/net/socket/SocketServerConnection.class
    10/16/18 05:14:36 AM IST [DEBUG] [IntroscopeAgent.BoundaryDetection] Rule: {UnconditionalSelectRule, selected = true} has marked element:{org.teiid.net.socket.SocketServerConnection.isOpen(SocketServerConnection.java:351), index: 17, size: 98} as candidate.
    10/16/18 05:14:36 AM IST [DEBUG] [IntroscopeAgent.AutomaticBackendDetection] WriteReadPatternDetector - Found Backend candidate: {org.teiid.net.socket.SocketServerConnection.isOpen(SocketServerConnection.java:351), index: 17, size: 98}
    10/16/18 05:14:36 AM IST [DEBUG] [IntroscopeAgent.AutomaticBackendDetection] Backend Candidates: [org.teiid.net.socket.SocketServerConnection.isOpen(SocketServerConnection.java:351)]
    10/16/18 05:14:41 AM IST [DEBUG] [IntroscopeAgent.IntelligentInstrumentation] FilePersistenceService - processing new request for persistence of method tracing directives: {org.teiid.net.socket.SocketServerConnection=[className: org.teiid.net.socket.SocketServerConnection, methods: {isOpen=[methodName: isOpen, descriptor: , trace types: [EXIT_POINT, EXIT_POINT_BACKEND, EXIT_POINT_ERROR_REPORTING]]}]}
    10/16/18 05:14:41 AM IST [DEBUG] [IntroscopeAgent.Agent] getting bytes for class -org.teiid.net.socket.SocketServerConnection

    10/16/18 05:14:41 AM IST [DEBUG] [IntroscopeAgent.Agent] searching for path -org/teiid/net/socket/SocketServerConnection.class
    10/16/18 05:14:41 AM IST [DEBUG] [IntroscopeAgent.IntelligentInstrumentation] FilePersistenceService - method tracing directives after filtration: {org.teiid.net.socket.SocketServerConnection=[className: org.teiid.net.socket.SocketServerConnection, methods: {isOpen()Lorg/teiid/client/util/ResultsFuture;=[methodName: isOpen, descriptor: ()Lorg/teiid/client/util/ResultsFuture;, trace types: [EXIT_POINT, EXIT_POINT_BACKEND, EXIT_POINT_ERROR_REPORTING]], isOpen(J)Z=[methodName: isOpen, descriptor: (J)Z, trace types: [EXIT_POINT, EXIT_POINT_BACKEND, EXIT_POINT_ERROR_REPORTING]]}]}
    10/16/18 05:14:41 AM IST [DEBUG] [IntroscopeAgent.IntelligentInstrumentation] FilePersistenceService - filtered out skipped and already persisted entries, new directives to persist: {org.teiid.net.socket.SocketServerConnection=[className: org.teiid.net.socket.SocketServerConnection, methods: {isOpen()Lorg/teiid/client/util/ResultsFuture;=[methodName: isOpen, descriptor: ()Lorg/teiid/client/util/ResultsFuture;, trace types: [EXIT_POINT, EXIT_POINT_BACKEND, EXIT_POINT_ERROR_REPORTING]], isOpen(J)Z=[methodName: isOpen, descriptor: (J)Z, trace types: [EXIT_POINT, EXIT_POINT_BACKEND, EXIT_POINT_ERROR_REPORTING]]}]}

     

    10/16/18 05:14:41 AM IST [DEBUG] [IntroscopeAgent.IntelligentInstrumentation] FilePersistenceService - final set of directives (existing + new) to persist: {org.teiid.net.socket.SocketServerConnection=[className: org.teiid.net.socket.SocketServerConnection, methods: {isOpen()Lorg/teiid/client/util/ResultsFuture;=[methodName: isOpen, descriptor: ()Lorg/teiid/client/util/ResultsFuture;, trace types: [EXIT_POINT, EXIT_POINT_BACKEND, EXIT_POINT_ERROR_REPORTING]], isOpen(J)Z=[methodName: isOpen, descriptor: (J)Z, trace types: [EXIT_POINT, EXIT_POINT_BACKEND, EXIT_POINT_ERROR_REPORTING]]}]}

    ===