DX Application Performance Management

  • Private Community

  • 1.  Monitoring Apache Tomcat

    Posted Mar 07, 2014 09:39 AM

    Hi,

    we are running a PoC to demonstrate the monitoring capabilities of CA APM.

    Some of the applications part of the scope are running on Apache Tomcat servers.

    My questions is that apart from Java Agent installation for Tomcat do we need to setup also an agent for Web servers?

    Are we going to get any metrics from the agent for web servers that we are not getting from the Java Agent?

    Also for load balancing they have multiple instances of tomcat on the same machine(on different ports). Should we use the same agent profile for all instances? Is this going to affect the way we see the metrics inside the console?

     



  • 2.  RE: Monitoring Apache Tomcat
    Best Answer

    Posted Mar 07, 2014 11:08 PM

    Hi Kostas,

    If you wish to get rich performance and availability metrics of web servers, you may use APM for WebServer but for standard monitoring of your application, java agent is good enough.

    Yes since APM for WebServer is an extensions, it will provide you additional metrics which standard java agent cannot suc as availability of webserver, worker process status, I/O, etc. These metrics may vary depending on webserver type. You may go through "APM for WebServer" bookshelf for more details.

    Regarding use of Agent profile file, if you wish to use same set of PBDs and rely on auto agent naming, you may share same "InroscopeAgent.profile" file amongst different instances of tomcat but if you are planning to give a custom name to all your tomcat instances, you may use multiple agent profiles. Eg.

    IntroscopeAgentA.profile

    IntroscopeAgentB.profile

    IntroscopeagentX.profile

    Hope this answers your questions.

     

    Regards,

    Mukesh Singh

     



  • 3.  RE: [CA APM General Discussion] RE: Monitoring Apache Tomcat

    Posted Mar 10, 2014 06:09 AM
    Hi,

    You don’t need multiple Agent profiles to give each instance a custom name (in fact you really want to avoid multiplying Agent profiles as much as possible, since you will have to manage and manually upgrade each of these). You just need to pass a java system property along with the other Introscope related arguments in the startup command line:

    -Dcom.wily.introscope.agent.agentName=TomcatServer1

    Or you can also reuse one of the existing system properties, for example if you already have a Java system property that contains the name of your JVM, in the IntroscopeAgent.profile just specify it in that property:
    introscope.agent.agentNameSystemPropertyKey=TOMCATINSTANCEID

    Regs,

    Florian.


  • 4.  RE: [CA APM General Discussion] RE: Monitoring Apache Tomcat

    Posted Mar 11, 2014 07:57 AM

    Thank you both.