DX Application Performance Management

Expand all | Collapse all

Application Deployment Process

Jump to Best Answer
  • 1.  Application Deployment Process

    Posted 11-15-2018 06:46 AM

    Hi team

     

    I have a java application in my environment that I have to monitor.

    Following are the steps I have done:

    1- Created the war file of the application using Eclipse

    2- Deployed the war file in the Tomcat Webapps folder

    I have started to see metrics regarding the frontend of the application but no database related metrics.

    is there any other way of deployment of the application?

    I cannot find any Application  deployment related document on docops.

     

    Thanks



  • 2.  Re: Application Deployment Process

    Posted 11-15-2018 09:14 AM

    Dear Imran:

    There is an excellent overview page on deployment. 

    Agent Deployment Guidelines - CA Application Performance Management - 10.7 - CA Technologies Documentation 

     

    Did you configure backend metric groups ?

     

    Configure Backend Path Groups - CA Application Performance Management - 10.7 - CA Technologies Documentation 

     

    What does the autoprobe and Agent log say when processing backend configuration/tracers?

     

    Thanks

    Hal German



  • 3.  Re: Application Deployment Process

    Posted 11-16-2018 12:03 AM

    Hi Hallett_German

    Thanks,but its not clear I am not talking about agent deployment I am talking about how we Start monitoring the Application as in what is the process of deployment of Apllication on the webserver.

     

    Thanks



  • 4.  Re: Application Deployment Process
    Best Answer

    Posted 11-16-2018 06:30 AM

    Hello Imran,

     

    If you don't see backends metrics, then I suggest you to check the below:

     

    1) Make sure there is JDBC activity 

     

    2) If could the a compatibility issue with "SQLAgent" agent extension, check the APM compatibility guide, you have 2 options:

     

    a) CA Application Performance Management Compatibility Guides - CA Technologies 

    select a version | select  APM Agent tab, go to the SQLAgent section

     

    b) Go to pcm:

    https://pcm.ca.com/dyntbl.php?mod=pclink&chgl_query=None&ef_lnk_cm_app_type=Agent&ef_lnk_cm_app_ver=None&ef_lnk_cm_to_ap… 

     

    Might I know what is the version in use?

    It could be the case that you would need extend the current PBDs

     

    3) Verify that the metric clamp from agent & EM have not been reached.

     

    Go to to the Workstation/Webview metric browser, expand the branch:


    Custom Metric Host (virtual)
    - Custom Metric Process (virtual)
    - Custom Metric Agent (virtual)(collector_host@port)(SuperDomain)
    - Agents
    - Host
    - Process
    - AgentName

     

    ensure "is Clamped" metric is zero

     

    do the same for the EM/collector, expand the branch

     

    Custom Metric Host (virtual)
    - Custom Metric Process (virtual)
    - Custom Metric Agent (virtual)(collector_host@port)(SuperDomain)
    - Enterprise manager
    - Connections

     

    ensure below metrics are 0
    - EM Historical Metric Clamped
    - EM Live Metric Clamped

     

    4) If possible try to test the issue using our latest 10.7 version, ensure smart instrumentation is enabled.

     

    In 10.5, we enhanced the Smart Instrumentation and introduced the  "Automatic Backend Detection" feature.

    Although it doesn't provide the same level of SQL metrics, it will give you at least the blamepoint metrics for the jdbc class in use. This feature requires:


    - SI should be enabled : introscope.agent.deep.instrumentation.enabled=true
    - DI should be enabled : introscope.autoprobe.dynamicinstrument.enabled=true
    - JVM 1.7, 1.8

     

    If this still doesn't work you might still need to extend the current OOTB instrumentation, I am afraid

    Agent Monitoring a Frontend Does Not Automatically Detect Backend - CA Application Performance Management - 10.7 - CA Te… 

     

    I hope this helps,

     

     

     

    Regards,

    Sergio