-
Problem report
-
Resolution: Unresolved
-
Critical
-
4.2.1
-
Any starting from Zabbix-Server 4.2+
-
Sprint 56 (Sep 2019), Sprint 55 (Aug 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019), Sprint 57 (Oct 2019), Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020), Sprint 61 (Feb 2020), Sprint 62 (Mar 2020), Sprint 63 (Apr 2020), Sprint 64 (May 2020), Sprint 65 (Jun 2020), Sprint 66 (Jul 2020), Sprint 67 (Aug 2020), Sprint 68 (Sep 2020), Sprint 69 (Oct 2020), Sprint 70 (Nov 2020), Sprint 71 (Dec 2020), Sprint 72 (Jan 2021), Sprint 73 (Feb 2021), Sprint 74 (Mar 2021), Sprint 75 (Apr 2021)
-
1
Steps to reproduce:
- Create a new Item with an uptade interval ov 1m
- Add a Preprocessing step "Discard with Heartbeat" and set it to 1h
- Wait a for some data to be collected (2-3h in this example)
Result:
See screenshot...
The result looks counter intuitive, as you think the values might not be fetched
Expected:
Connecting the dots if the "Discard .*" Preprocessing step is added as we KNOW the values have been there.
May be dont draw the lines if the connection was really dropped, but Idk if those stati are somewhere visible to the Item when drawing a graph.
- causes
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
ZBX-17847 2 day graphs embedded in screens have missing data
-
- Closed
-
- depends on
-
ZBXNEXT-8416 zabbix avg calculation wrong when measurement interval is not constant
-
- Confirmed
-
-
ZBXNEXT-5691 increase 'float' precision & data length (frontend)
-
- Closed
-
- is duplicated by
-
ZBXNEXT-9004 Calculating the trigger value when throttling
-
- Reopened
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
ZBX-24034 Calculating the value when trottling.
-
- Closed
-
