DX Application Performance Management

Expand all | Collapse all

CA APM Docker Monitor parse issues

Jump to Best Answer
  • 1.  CA APM Docker Monitor parse issues

    Posted 05-29-2017 05:25 PM

    Hi Community,

     

    I'm using CA APM Docker extension from CA Marketplace and works fine but for some docker hosts have parsing errors for example from DockerAgent.log:

     

    Integer: out of range "throttled_time" variable.

    Caused by: com.fasterxml.jackson.core.JsonParseException: Numeric value (97116495725) out of range of int
    at [Source: {"read":"2017-05-29T20:03:23.681980199Z","precpu_stats":{"cpu_usage":{"total_usage":0,"percpu_usage":null,"usage_in_kernelmode":0,"usage_in_usermode":0},"system_cpu_usage":0,"throttling_data":{"periods":0,"throttled_periods":0,"throttled_time":0}},"cpu_stats":{"cpu_usage":{"total_usage":398325736557,"percpu_usage":[95191697442,122018354078,79927102452,101188582585],"usage_in_kernelmode":110380000000,"usage_in_usermode":217630000000},"system_cpu_usage":1716532970000000,"throttling_data":{"periods":590792,"throttled_periods":816,"throttled_time":97116495725}},"memory_stats":.........

     

    String parse to Integer:

     

    5/29/17 03:06:22 PM PET [INFO] [com.ca.apm.fieldpacks.docker.DataPoller] Total no of containers found : 2
    java.lang.NumberFormatException: For input string: "585.7 kB"

     

    It's possible fix this parse errors ?

     

    Regards !

     

    Aldo 



  • 2.  Re: CA APM Docker Monitor parse issues

    Broadcom Employee
    Posted 05-30-2017 10:03 AM

    Dear Aldo:

    I am asking in internal forums for someone to respond. No guarantee this will happen. But people are aware of your question

    Thanks

    Hal German



  • 3.  Re: CA APM Docker Monitor parse issues
    Best Answer

    Broadcom Employee
    Posted 05-30-2017 12:15 PM

    Dear Aldo:

         We are likely going to open a defect for this based on internal discussions. The best way to ensure that happens is opening a case.There is likely a later version of Docker Monitor that should resolve this.  Please do so and report back the case number and the resolution at a later date to help others

     

    Thanks

    Hal German