ZABBIX FEATURE REQUESTS
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-1179

Inconsistency in the report how many time the processes spent.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.8
    • Component/s: Server (S)
    • Labels:
    • Environment:
      tested 1.8.9 release
      DebugLevel=4

      Description

              • Exist for the processes: *****
                21845:20111127:125745.860 configuration syncer spent 0.003662 second while processing configuration data
                21845:20111127:125745.860 sleeping for 60 seconds

      21868:20111127:121357.596 escalator #1 spent 0.000639 seconds while processing escalations
      21868:20111127:121357.596 sleeping for 3 seconds

      21864:20111127:125832.064 history syncer #1 spent 0.010309 seconds while processing 5 items
      21864:20111127:125832.064 sleeping for 5 seconds

              • Exist for processes but not the previous line before the "sleep for <N> seconds": *****
                21863:20111127:121646.073 discoverer #1 spent 0.000544 seconds while processing rules
                21863:20111127:121646.073 query [txnlev:0] [select count,min(nextcheck) from drules where proxy_hostid=0 ......
                21863:20111127:121646.073 get_minnextcheck(): no items to update
                21863:20111127:121646.073 sleeping for 60 seconds

      21862:20111127:125846.720 http poller #1 spent 0.000754 seconds while updating HTTP tests
      21862:20111127:125846.720 query [txnlev:0] [select min(t.nextcheck) from httptest t,applications a,hosts h ..........
      21862:20111127:125846.720 No httptests to process in get_minnextcheck.
      21862:20111127:125846.720 sleeping for 5 seconds

      21858:20111127:125837.962 icmp pinger #1 spent 0.000311 seconds while processing 0 items
      21858:20111127:125837.962 In DCconfig_get_poller_nextcheck() poller_type:3
      21858:20111127:125837.962 End of DCconfig_get_poller_nextcheck():1322391540
      21858:20111127:125837.962 sleeping for 5 seconds

      21848:20111127:131841.222 poller #2 spent 0.002886 seconds while updating 1 values
      21848:20111127:131841.222 In DCconfig_get_poller_nextcheck() poller_type:0
      21848:20111127:131841.222 End of DCconfig_get_poller_nextcheck():1322392733
      21848:20111127:131841.222 sleeping for 5 seconds

      21869:20111127:121355.424 proxy poller #1 spent 0.000201 seconds while processing 0 proxies
      21869:20111127:121355.424 In DCconfig_get_proxypoller_nextcheck()
      21869:20111127:121355.424 End of DCconfig_get_proxypoller_nextcheck():-1
      21869:20111127:121355.424 sleeping for 5 seconds

      21852:20111127:121356.178 unreachable poller #1 spent 0.000221 seconds while updating 0 values
      21852:20111127:121356.178 In DCconfig_get_poller_nextcheck() poller_type:1
      21852:20111127:121356.178 End of DCconfig_get_poller_nextcheck():-1
      21852:20111127:121356.178 sleeping for 5 seconds

              • The line "<process> spent NNN seconds ..." is missing for the processes: *****
                alerter
                db watchdog
                housekeeper
                main process
                self-monitoring
                timer
                trapper
                node watcher

        Activity

        Hide
        Alexei Vladishev added a comment -

        I am closing it.

        Show
        Alexei Vladishev added a comment - I am closing it.
        Hide
        richlv added a comment -

        believing in consistency, i moved this to zbxnext & reopened it.
        debugging zabbix is a bit hard, so consistent logging is highly desirable. i'd classify this as a minor bug, but if not, zbxnext might do

        again, feel free to close if this definitely won't be fixed

        Show
        richlv added a comment - believing in consistency, i moved this to zbxnext & reopened it. debugging zabbix is a bit hard, so consistent logging is highly desirable. i'd classify this as a minor bug, but if not, zbxnext might do again, feel free to close if this definitely won't be fixed
        Hide
        Alexander Vladishev added a comment -

        Related issue: ZBXNEXT-1855

        Show
        Alexander Vladishev added a comment - Related issue: ZBXNEXT-1855
        Hide
        Andris Mednis added a comment -

        Available in the development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-1855-2. Also contains a solution for ZBXNEXT-1855.

        Show
        Andris Mednis added a comment - Available in the development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-1855-2. Also contains a solution for ZBXNEXT-1855 .
        Hide
        Andris Zeila added a comment -

        Successfully tested

        Show
        Andris Zeila added a comment - Successfully tested
        Hide
        Andris Mednis added a comment -

        Fixed in version pre-2.1.8 r39449.

        Show
        Andris Mednis added a comment - Fixed in version pre-2.1.8 r39449.

          People

          • Assignee:
            Unassigned
            Reporter:
            Oleksiy Zagorskyi
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: