Trigger switches to problem state incorrectly

XMLWordPrintable

    • Type: Incident report
    • Resolution: Incomplete
    • Priority: Major
    • None
    • Affects Version/s: 2.0.9
    • Component/s: Server (S)
    • None
    • Environment:
      Centos 6.4 x64, Postgresql 9.2.5

      I have a trigger that sometimes works just plain wrong. Most of the time it works well, but every now and then it'd fire without any reason.

      Trigger expression:

      {Template_app1:executors.max(3600)}<7 & {Template_app1:job_queue_length.max(3600)}>50
      

      Action message:

      {TRIGGER.NAME}: {STATUS}
      Executors number: {ITEM.VALUE1}
      Queue length: {ITEM.VALUE2}
      Event ID: {EVENT.ID}
      

      (I have also tried "

      {ITEM.LASTVALUE1/2}

      ", it doesn't make any difference)

      Actual received message:

      App1 is missing executors on srv20: PROBLEM
      Executors number: 0
      Queue length: 1
      Event ID: 3138872
      

      That just shouldn't be happening, should it? I checked the graphs, checked values in the database directly. The notification is correct, the trigger shouldn't have fired.
      Both items are Numeric(unsigned), Decimal.

            Assignee:
            Unassigned
            Reporter:
            Ilya I.
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: