DX Application Performance Management

  • 1.  I would like to know how to use CLW to track transactions in excess of 2 seconds without Trace Period limit.

    Posted Aug 11, 2018 12:47 AM

    Hello.. .

    CA APM Version v10.7

    I would like to know how to use CLW to track transactions in excess of 2 seconds without Trace Period limit.

     

    In other words, how do we exclude the "for 600 seconds" tracking Period constraint from the CLW command below?

     

    java -Xmx128M -Duser=Admin -Dpassword= -Dhost=localhost -Dport=5001 -jar <Introscope Home>\lib\CLWorkstation.jar trace transactions exceeding 2 seconds in agents matching "(.*)" for 600 seconds

     

    Thank you..

     

    Additional: How do I Abort CLW Transaction Tracing?



  • 2.  Re: I would like to know how to use CLW to track transactions in excess of 2 seconds without Trace Period limit.

    Broadcom Employee
    Posted Aug 12, 2018 07:08 PM


  • 3.  Re: I would like to know how to use CLW to track transactions in excess of 2 seconds without Trace Period limit.

    Posted Aug 13, 2018 03:29 AM

    How do I Abort CLW Transaction Tracing? 



  • 4.  Re: I would like to know how to use CLW to track transactions in excess of 2 seconds without Trace Period limit.

    Broadcom Employee
    Posted Aug 13, 2018 04:42 AM

    Hi Jinsuk,

    You just terminate the CLW java process with Ctrl-C or kill etc.

    Regards,

    Lynn



  • 5.  Re: I would like to know how to use CLW to track transactions in excess of 2 seconds without Trace Period limit.

    Posted Aug 13, 2018 06:13 AM

    Hello.

     

     

     

    Yes, I did, but it doesn't stop for the setted time period.

     

     

     

    CLW was killed, But transactions continue to be collected during setted time period.

     

     

     

    If I press "Ctrl+C" CLW was killed. but, transactions continue to be collected during setted time period.

     

     

     

    For example, if you specify "for 1800 seconds" the transaction is unconditionally collected for 1800 seconds even if CLW was Killed.

     

     

     

    However, restarting EM and TOMCAT at the same time will stop the transaction collection.

     

     

     

    What should I do?

     

     

     

    Thank you



  • 6.  Re: I would like to know how to use CLW to track transactions in excess of 2 seconds without Trace Period limit.

    Posted Aug 13, 2018 04:54 AM

    Yes, I did, but it doesn't stop for the setted time period.

    CLW was killed, But transactions continue to be collected during setted time period.

    If I press "Ctrl+C" CLW was killed. but, transactions continue to be collected during setted time period.

    For example, if you specify "for 1800 seconds" the transaction is unconditionally collected for 1800 seconds even if CLW was Killed.

    However, restarting EM and TOMCAT at the same time will stop the transaction collection.

    What should I do?



  • 7.  Re: I would like to know how to use CLW to track transactions in excess of 2 seconds without Trace Period limit.

    Broadcom Employee
    Posted Aug 13, 2018 06:10 PM

    Hi Jinsuk,

    I have taken ownership of the support case you raised for this scenario - I will investigate further and get back to you. Once concluded I  then post back here for community benefit.

     

    Regards,

     

    Lynn



  • 8.  Re: I would like to know how to use CLW to track transactions in excess of 2 seconds without Trace Period limit.
    Best Answer

    Broadcom Employee
    Posted Aug 13, 2018 07:41 PM

    After further research Support have confirmed that it is not possible to stop a transaction trace session that has been started with the CLW before the session duration time has elapsed. Therefore we suggest to exercise caution with the length of duration times used when running transaction traces from CLW. Also particularly when running CLW in a scripted format where the command could be issued easily many times, as this could easily lead to a large volume of trace processing which will increase performance overhead on all parts of the product.
    A new KB article has also been published with more extensive details:
    "Can I stop a transaction trace session started by the CA APM Command Line Workstation (CLW)?"
    https://comm.support.ca.com/kb/can-i-stop-a-transaction-trace-session-started-by-commandline-workstation/KB000067263

    Thanks to my colleague DavidLewis for notifying me of the previous research he did on this subject.