Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  2. ZBX-14503

Template App Generic Java JMX review


    • Sprint 57 (Oct 2019), Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020), Sprint 61 (Feb 2020), Sprint 62 (Mar 2020), Sprint 63 (Apr 2020), Sprint 64 (May 2020), Sprint 65 (Jun 2020), Sprint 66 (Jul 2020), Sprint 67 (Aug 2020)
    • 1

      Steps to reproduce:
      1) triggers in template Template App Generic Java JMX about Heap memory being fully committed like "mem Heap/Non-Heap Memory fully committed on {HOST.NAME}" seems to be not very useful - as far as I understand, having it fully committed is quite fine, especially on systems with enough memory.

      Monitoring of allocated memory for variables, objects and program code in the context of the latest value does not carry useful information. And triggers will give frequent false positives. Alarm about Heap memory should only be if memory is not cleaned after several passes of the garbage collector.
      But rather monitor the garbage collector.

      2. triggers about memory usage like "70% mem Heap Memory used on {HOST.NAME}" seem to be set at a very low threshold - java memory is often expected to fill up to be cleaned up by gc a bit later. as such, it might make more sense to check for >90% full for 10 minutes or even more.

      Reviewed the template Template App Generic Java JMX.

            tuskov Tikhon Uskov (Inactive)
            neogan Andrei Gushchin (Inactive)
            Team INT
            0 Vote for this issue
            8 Start watching this issue