DX Application Performance Management

  • 1.  Can we monitor which process is responsible for the CPU going high in Introscope?

    Posted Mar 27, 2015 11:29 AM

    I can see 5 Processors under CPU in Introscope. What does that mean?

    Also for eg. If the CPU Utilization goes high due to opening of a big file in Production environment, how and where can we drill down and show the exact reason for CPU of particular process going high?



  • 2.  Re: Can we monitor which process is responsible for the CPU going high in Introscope?
    Best Answer

    Posted Mar 28, 2015 12:23 AM

    Hi Pvpalval,

    Please find my comments inline.

     

    I can see 5 Processors under CPU in Introscope. What does that mean?

    --> These are the hardware processors 5 core CPU Processor machine. And the values you are getting is the CPU Utilization (Aggregate %) on that individual processor by all system and java processes.

     

    Also for eg. If the CPU Utilization goes high due to opening of a big file in Production environment, how and where can we drill down and show the exact reason for CPU of particular process going high?
    -->To answer your question, it is not possible to drill down to know exactly which PID(Process) or System user is utilizing high CPU from Wily. You can only make out a difference using '% process' and '% aggregate' value, Where -
    '% process' - indicates CPU Utilization by JVM process running on to that server which Wily agent is instrumented with. [And to my experience, if it goes beyond 9-10% value, there is some issue in the application]

    '% aggregate' - indicates CPU Utilization by all processes (including system level) and that too per processor.

     

    Actually if you ask me, this sometimes gets very confusing if you say to a developer\Prod management. That is the reason if I see some high '% process' value, I run $ Top command on my Linux boxes to know which particular PID is consuming high CPU.

     

    Hope it helps.

     

    Regards,

    Vaibhav



  • 3.  Re: Can we monitor which process is responsible for the CPU going high in Introscope?

    Posted Mar 30, 2015 09:26 AM

    Thanks Vaibhav..



  • 4.  Re: Can we monitor which process is responsible for the CPU going high in Introscope?

    Posted Apr 01, 2015 06:11 AM

    Hi Vaibhav,

     

    When I see on Investigator, CPU Utilization % (process) is showing 3% and both the processor Utilization % (aggregate) is fluctuating around 10 to 12%.

     

    But when we run TOP command for the same fuse box, there it shows CPU Utilization as 94% sumtimes. So how shall we make out which values are referred to each other

    ?



  • 5.  Re: Can we monitor which process is responsible for the CPU going high in Introscope?

    Broadcom Employee
    Posted Apr 01, 2015 11:41 PM
      |   view attached

    Please refer to the attachment for an explanation of CPU metrics from Java Agents.

    Attachment(s)



  • 6.  Re: Can we monitor which process is responsible for the CPU going high in Introscope?

    Broadcom Employee
    Posted Apr 02, 2015 12:02 AM

    For multi-cpu Linux servers KB TEC612272 may also help understanding:

    On a 4xCPU multi-processor Linux server the agent metric "CPU:Utilization % (process)" consistently shows a much lower value compared to the CPU utilization reported by the "top" command for the agent/java process.

    http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec612272.aspx



  • 7.  Re: Can we monitor which process is responsible for the CPU going high in Introscope?

    Broadcom Employee
    Posted Apr 02, 2015 12:27 PM

    Hi Pvpalval,

     

    Note that this requirement is a border case between APM and infrastructure management. As noted above CA APM focuses on how much CPU the app server Java process is taking and not on what other processes are using.

     

    To get info on which processes are taking CPU in CA APM you can use EPAgent plugins e.g. RHEL_VmStat.zip on Linux or PerfMonCollector Service Agent on Windows.

     

    Ciao,

    Guenter