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

Unnecessary SQL queries while processing trigger escalations in maintenance period

XMLWordPrintable

    • Sprint 9, Sprint 10, Sprint 11, Sprint 12, Sprint 13
    • 5

      Escalator process performs many SQL queries beforemaintenance mode check:

       15623:20170602:130549.296 query [txnlev:0] [select escalationid,actionid,triggerid,eventid,r_eventid,nextcheck,esc_step,status,itemid from escalations where triggerid is not null order by actionid,triggerid,itemid,escalationid]
       15623:20170602:130549.306 query [txnlev:0] [select actionid,name,status,eventsource,esc_period,def_shortdata,def_longdata,r_shortdata,r_longdata,maintenance_mode from actions where actionid=100100000000005]
       15623:20170602:130549.307 query [txnlev:0] [select null from operations where actionid=100100000000005 and recovery=1]
       15623:20170602:130549.308 query [txnlev:0] [select eventid,source,object,objectid,clock,value,acknowledged,ns from events where eventid=626686]
       15623:20170602:130549.309 query [txnlev:0] [select tag,value from event_tag where eventid=626686]
       15623:20170602:130549.310 query [txnlev:0] [select description,expression,priority,comments,url,recovery_expression,recovery_mode from triggers where triggerid=2581059]
       15623:20170602:130549.311 In check_escalation() escalationid:54428 status:active
       15623:20170602:130549.311 End of check_escalation():skip error: '(null)'
      

      It is better to use such information from DC/execute queries after performing maintenance and other DC checks or use bulk requests.

            Unassigned Unassigned
            dotneft Alexey Pustovalov
            Team C
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: