*unknown* ??

[lou.degenaro]

My trigger's expression is:

---
{testducc:web.test.fail["[testducc] DUCC"].last()}>0
---

The e-mail sent by Zabbix contains:

---
testducc: DUCC status
Trigger status: OK
Trigger severity: Warning
Trigger URL:

Item values:

1. Failed step of scenario "[testjducc] DUCC". (testducc:web.test.fail["[testducc] DUCC"]): 0
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
---

Why do I get 2. and 3. *UNKNOWN* and how do I get rid of them!?

Thanks.

Lou.

[LenR]

It's from the default message in the action, the default is to send the first 3 item names and values, since you only have 1 item, the others are unknown.

You uncheck "use default message" and just delete the parts for items 2 & 3.

I suggested for actions, "unknown" be null, then the message would self configure to the number of items, but I either didn't explain it well enough or no one else likes the idea :-)

[lou.degenaro]

Not sure I understand.

Under Configuration -> Actions I select my action's Name and go to a new page that has boxes for: Name, Default subject, Default message...

For Default message I see 3 entries:

===
Item values:

1. {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1}
2. {ITEM.NAME2} ({HOST.NAME2}:{ITEM.KEY2}): {ITEM.VALUE2}
3. {ITEM.NAME3} ({HOST.NAME3}:{ITEM.KEY3}): {ITEM.VALUE3}

Original event ID: {EVENT.ID}
===

I deleted the last two and Updated and now see this:

===
Item values:

1. {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1}

Original event ID: {EVENT.ID}
===

But when I force the event I still get e-mail with:

===
1. Response code for step "Home Page" of scenario "DUCC Web Server". (bluejws67:web.test.rspcode[DUCC Web Server,Home Page]): 0
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*

Original event ID: 370
===

Thanks.

Lou.

[LenR]

Ok, check to see if the action's operation that sends this message has "Default Message" checked. If not, you have to edit the message in that action.

Also check the default message to be sure it's saved as you intended.

[lou.degenaro]

No joy.

Please see attachment.

[LenR]

Post the Operation section that sends the email

[lou.degenaro]

Problem solved: user error

Turns out there were 2 Zabbix servers running each on a different host. I had thought one of them was retired, but it was still running. Enough said.

[LenR]

I call that "Dead Armadillo" debugging, sometimes you just have to stand in the traffic and see which way it's going....

[louis-m]

I normally create a TESTING alert and place a load of variables eg Item Value 2 = {ITEM.VALUE2} in there under a heading of For debugging Only.
The default alert only gets the values I know it needs eg {ITEM.VALUE1} etc

If testing, i temporarily disable the live alerts (to all admins etc), enable the test alert (only to myself) and then when the message comes through, I can see what variables it's chucking through with it.