Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-9622

Add top.peak in diaginfo to identify items that had high queue

XMLWordPrintable

    • S24-W48/49
    • 1

      Send 1000 values for trapper item with preprocessing, each 1 MB

      See that 771 MB is consumed until malloc_trim is called

       771.17 Mb ./sbin/zabbix_server: preprocessing manager #1 [queued 1, processed 3 values, idle 5.154571 sec during 5.155190 sec]
      

      Check diaginfo and see that there is no helpful information:

      == preprocessing diagnostic information ==
      Cached items:5 pending tasks:0 finished tasks:0 task sequences:0 time:0.000530
      Top.sequences:
      

      Expected, it should be possible to identify items that received many values at once to identify what causes such high peak memory usage

      == preprocessing diagnostic information ==
      Cached items:5 pending tasks:0 finished tasks:0 task sequences:0 time:0.000530
      Top.sequences:
      
      Top.peak:
      1278554:20241127:154042.942   itemid:47740 tasks:1000
      

      Actual:
      It is only possible to identify such items when they are being processed for example:

      == preprocessing diagnostic information ==
      Cached items:5 pending tasks:165 finished tasks:0 task sequences:1 time:0.010465
      Top.sequences:
        itemid:47740 tasks:168
      

      This could help when diagnosing issues as ZBX-25050

            kseve Kirils Seve
            vso Vladislavs Sokurenko
            Team B
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: