[ZBX-21967] Incorrect problem duration calculation Created: 2022 Nov 23 Updated: 2023 Oct 07 |
|
| Status: | Confirmed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 6.2.5 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Minor |
| Reporter: | Egor T. | Assignee: | Zabbix Development Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
zabbix_server (Zabbix) 6.2.0 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
In case of service oriented monitoring structure like below:
Service based notifications was configured. We interested to receive notification only from top level service if service status changing. We need to send notification if service in "High" or "Disaster" status. In case of status changed like this OK->High(or disaster)->OK.: No problem But if status change lie this: OK->Average->High->Average->OK We are receiving negative time:
Below you can see events:
Look like this operate like this:
I think that negative time itself for problem duration - problem. Service level actions and notification should be not the same as trigger based. |
| Comments |
| Comment by Egor T. [ 2022 Nov 28 ] |
|
More correct picture:
|
| Comment by Aigars Kadikis [ 2022 Nov 30 ] |
|
Hi Egor, Thank you for contacting Zabbix. I think the surface level root cause is that the default media type is using EVENT.DURATION macro: |
| Comment by Egor T. [ 2022 Dec 01 ] |
|
Hello. Thank you for your reply. Do you have plan for that? |