[ZBX-3003] time period suffixes do not work in item references Created: 2010 Sep 14  Updated: 2017 May 30  Resolved: 2012 Jul 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: None
Fix Version/s: 2.0.2rc1, 2.1.0

Type: Incident report Priority: Major
Reporter: richlv Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: maps, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

try using time period suffixes while referencing item data in map labels - that fails.

for example, avg(10m) fails (but avg(600) succeeds)



 Comments   
Comment by Alexey Fukalov [ 2012 Jul 02 ]

dev branch: svn://svn.zabbix.com/branches/dev/ZBX-3003

Comment by richlv [ 2012 Jul 02 ]

(1) elsewhere we support up to yotta, but here only up to tera was added (which would have been nice to mention in the comments )

what's the reason for that ?

<Vedmak> Where else we support Y in trigger expressions? As it seems to be "Simple macros as used in trigger expressions." and server support only up to T it can be confusing.
Where are docs how these macros should work (also related to ZBX-3782), from current docs i see these macros are same as in trigger expressions.

<richlv> according to http://www.zabbix.com/documentation/2.0/manual/config/triggers/suffixes#prefix_symbols , server should support up to t, frotend up to y (no exceptions listed)

<Vedmak> We decided to leave as it is, but update documentation.

Comment by Pavels Jelisejevs (Inactive) [ 2012 Jul 05 ]

(2) The K, M and other suffixes should use the 1024 multiplier instead of 1000. And for some reason the "w" suffix appears twice in the case statement.

<richlv> main reason being "server does it that way", so we go for consistency

<Vedmak> RESOLVED

<pavels> CLOSED.

Comment by Pavels Jelisejevs (Inactive) [ 2012 Jul 06 ]

TESTED.

Don't forget about (1).

Comment by Alexey Fukalov [ 2012 Jul 06 ]

Fixed in pre-2.0.2rc2 r28720, pre-2.1.0 r28721

Generated at Fri Apr 26 21:31:15 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.