-
Problem report
-
Resolution: Fixed
-
Trivial
-
3.0.28, 4.0.10
-
None
-
Sprint 56 (Sep 2019), Sprint 55 (Aug 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), Sprint 76 (May 2021), Sprint 77 (Jun 2021), Sprint 78 (Jul 2021), Sprint 79 (Aug 2021), Sprint 80 (Sep 2021), Sprint 81 (Oct 2021), Sprint 82 (Nov 2021), Sprint 83 (Dec 2021), Sprint 84 (Jan 2022), Sprint 85 (Feb 2022), Sprint 86 (Mar 2022), Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022), Sprint 90 (Jul 2022), Sprint 91 (Aug 2022), Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023), Sprint 98 (Mar 2023), Sprint 99 (Apr 2023), Sprint 100 (May 2023), Sprint 101 (Jun 2023)
-
1
Value at the beginning of the graph is ignored.
Items that are being monitored every 1 day at 00:00 and usually it comes in less than "1".
If you get spike values at the start time, a graph with missing values may be drawn.
... 2019-05-04 23:59:59 1556981999 0.377 2019-05-04 00:00:00 1556895600 0.272 2019-05-02 23:59:59 1556809199 0.224 2019-05-02 00:00:00 1556722800 0.667 2019-05-01 00:00:00 1556636400 3.232 <-- 3
- 2019-04-30 23:50:00 ~ 2019-06-01 00:00:00 (Problem case)
2019-05-01 00:00:00 - 3.232 is not shown even if 10 min ago. This situation makes the graph misleading.
1 hour back, you can see the right value.
- 2019-04-30 23:00:00 ~ 2019-06-01 00:00:00 (Normal)
