Ad Widget

Collapse

Zabbix 3.0.2 Mail giving *UNKNOWN* value on macros

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MightBeAWizard
    Member
    • May 2016
    • 33

    #1

    Zabbix 3.0.2 Mail giving *UNKNOWN* value on macros

    So I set up sending alarms to email, at first it worked like it should (except that it sends new mail every 30 seconds). When mail came, it gave information about on what host is this incident happening, what is happening there etc etc.
    However after 10 sent mails almost every macro value started giving *UNKNOWN* value, with the expception on Original event ID, that is still giving values, everything else is like:

    Trigger: Disk Health on *UNKNOWN* NOT ok!
    Trigger status: PROBLEM
    Trigger severity: High
    Trigger URL:

    Item values:

    1. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN* 2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN* 3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*

    Any ideas why it is doing this?
    Last edited by MightBeAWizard; 28-06-2016, 14:40. Reason: Title updated
  • MightBeAWizard
    Member
    • May 2016
    • 33

    #2
    Also here is my trigger:

    {Template RAID:eventlog[System,,"Information|Warning|Error","HP Smart Array",,,skip].logsource("HP Smart Array")}=1 and {Template RAID:eventlog[System,,"Information|Warning|Error","HP Smart Array",,,skip].logseverity(0)}>1 and {Template RAID:eventlog[System,,"Information|Warning|Error","HP Smart Array",,,skip].nodata(30)}

    In latest data it shows information as it should.

    Comment

    • MightBeAWizard
      Member
      • May 2016
      • 33

      #3
      After trying to modify triggers and mail settings and then making them back as they were, it sends mail with correct information, no idea why... Now I would still like to know how I can prevent it sending same mail every 30 seconds, it would be fine if it sent it only once every hour or so. Spamming mailbox isn't really helping anyone :S

      Comment

      • MightBeAWizard
        Member
        • May 2016
        • 33

        #4
        After hours and hours of trial and error things finally work...

        Trigger:
        {Template RAID:eventlog[System,,"Information|Warning|Error","HP Smart Array",,,skip].logsource("HP Smart Array")}=1 and {Template RAID:eventlog[System,,"Information|Warning|Error","HP Smart Array",,,skip].logseverity(0)}>1 and {Template RAID:eventlog[System,,"Information|Warning|Error","HP Smart Array",,,skip].nodata(30)}

        Multiple PROBLEM events generation, unchecked.

        Item:

        Type: Agent(active)
        key: eventlog[System,,"Information|Warning|Error","HP Smart Array",,,skip]
        Type of information: Log
        Update interval: 60
        Log time format: pppppp:yyyyMMdd:hhmmss

        Now Trigger activates when problem is detected from eventlog, and it clears out when disk is back to normal state, send mail when problem is detected and sends ok mail when back to normal state.

        Hope this helps someone someday

        Comment

        • MightBeAWizard
          Member
          • May 2016
          • 33

          #5
          After deploying same trigger behind proxy, I don't know if it is really working or not, events give "Unknown" status, latest data gives "OK" and trigger status gives
          "Cannot evaluate function xxx.xxx.xxx.xxx:eventlog[System,,"Information|Warning|Error","HP Smart Array",,,skip].logsource("HP Sma"... so it basically gives error about that trigger.

          However it says status is OK, latest data gives "OK" and it checks it every hour, last change is "Never" cos it has been working and because of that ACK gives "No Events"... Or that is how I think it works(?)

          Latest Data for last 3 hours:
          2016-06-28 14:46:30
          OK
          2016-06-28 13:46:30
          OK
          2016-06-28 12:46:30
          OK

          So now I am just confused if it really works or not?

          Hope my post wasn't too messy :S

          *EDIT Latest data giving "OK" was from another trigger that I thought I deleted earlier, so it's irrelevant, still not working behind proxy tho :S

          **2nd EDIT: I made second trigger just to test eventlog, turns out it works like it should and my first hunch was correct, trigger status will stay Unknown until there is new error in eventlog, over and out!
          Last edited by MightBeAWizard; 29-06-2016, 11:01.

          Comment

          Working...