DX Unified Infrastructure Management

 View Only

  • 1.  wasp - log format - 23.4.5 - changed

    Posted 13 hours ago

    Hi!

    Was it intend to change the format?

    Aug 19 08:35:54:552 DEBUG [main, com.nimsoft.nimbus.probe.service.wasp.WaspLifecycleListener] Memory Status: Max Limit: 3641MB, Allocated: 2907MB, Free: 1649MB, Used: 1258MB
    Aug 19 08:35:58:117 DEBUG [main, com.nimsoft.nimbus.probe.service.wasp.WaspLifecycleListener] Memory Status: Max Limit: 3641MB, Allocated: 2907MB, Free: 1213MB, Used: 1694MB
    Aug 19 08:35:58:133 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Probe stopped.
    Aug. 19 08:40:46:323 INFO  [main, com.nimsoft.nimbus.NimProbeBase] Login to NimBUS is OK
    Aug. 19 08:40:46:339 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.WaspNimProbe] WaspNimProbe login successful.

    There is a useless "dot" after the month... a useless char.

    The lines till "Probe stopped" is the old wasp, afterwards the 23.4.5

    Some parsers (like my logview plus) breaks with that change, proppably some monitoring will be also if you extract the month with the know 3signs

    can that be configured or fixed?

    cheers
    Matthias



    -------------------------------------------


  • 2.  RE: wasp - log format - 23.4.5 - changed

    Broadcom Employee
    Posted 5 hours ago

    We will look into this and get back to you - I suspect it could be related to the change from Java8 to Java21, there may have been a change in some library that produces timestamps, but that is a guess at this point.

    -------------------------------------------