[ZBX-19777] Misleading wording for supported trigger functions with time ranges specification Created: 2021 Aug 04  Updated: 2024 Apr 10  Resolved: 2021 Sep 06

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: None
Fix Version/s: 6.0 (plan)

Type: Documentation task Priority: Trivial
Reporter: Andrey Tocko (Inactive) Assignee: Martins Valkovskis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2021-08-04-18-57-35-305.png    
Issue Links:
Causes
Sub-task
part of ZBX-19757 Functions Documentations needs to be ... Closed
Team: Team A
Sprint: Sprint 79 (Aug 2021)
Story Points: 1

 Description   

Hello Team!
It is not obvious to many users, that function with time range will calculate values within defined time range based on last value received and not current server time.
As Example let's imagine trapper item that was received week ago:

host:trapper_item.count(10m)>5

Users expects to count values received per 10 last minutes from NOW() on server.
But in reality it is 10 minutes range week ago.

Current wording in documentation is misleading and could be improved.

 Comments   
Comment by Martins Valkovskis [ 2021 Aug 25 ]

The footnotes for 'evaluation period' of the relevant functions have been updated in the supported versions: 4.0, 5.0, 5.4, 6.0,

by adding this text 

The evaluation period is up to the latest collected value (not the server 'now' time).
Generated at Sat Apr 19 00:20:35 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.