[ZBX-3568] *UNKNOWN* value received if use macros in an item key Created: 2011 Feb 25 Updated: 2017 May 30 Resolved: 2011 Mar 04 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 1.8.4 |
Fix Version/s: | 1.8.5 |
Type: | Incident report | Priority: | Critical |
Reporter: | Alexander Vladishev | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
Setting details: Hostname: localhost Trigger: {localhost:log[/var/log/{HOSTNAME} .log].str(error)}=1 Action message: {{HOSTNAME}: {TRIGGER.KEY}.last(#1)}{{HOSTNAME}:{TRIGGER.KEY} .last(#2)} {{HOSTNAME}:{TRIGGER.KEY} .last(#4)} Received: UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN It seems the problem is caused by escalator expands macros in item key's option. (1) Item key setting: log[/var/log/{HOSTNAME}.log] (2) Expand {TRIGGER.KEY} macro by escalator: log[/var/log/localhost.log] (1) and (2) is not equal, so escalater can not handle history data correctly. .log] item used hisotry of log[/var/log/localhost.log]. |
Comments |
Comment by Alexander Vladishev [ 2011 Feb 25 ] |
The server side fixed in version pre1.8.5, r18088. |
Comment by richlv [ 2011 Feb 25 ] |
could this be a duplicate of |
Comment by Alexander Vladishev [ 2011 Feb 25 ] |
Yes, of course! |
Comment by Alexander Vladishev [ 2011 Mar 04 ] |
Fixed in version pre1.8.5, r18258. |