[ZBX-9522] Frontend messaging on dashboard doesn't follow refresh period configuration. Created: 2015 Apr 27  Updated: 2024 Apr 10  Resolved: 2019 Aug 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 2.0.14, 2.2.9
Fix Version/s: 4.0.12rc1, 4.2.6rc1, 4.4.0alpha2, 4.4 (plan)

Type: Problem report Priority: Minor
Reporter: Kazuo Ito Assignee: Mārtiņš Tālbergs (Inactive)
Resolution: Fixed Votes: 1
Labels: globalmessages, guimessages, refresh
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Selection_364.png     PNG File Selection_427.png     File ZBX-9522-3.0.tar.gz     File ZBX-9522-3.0.v2.tar.gz     File __notify.php     File example.ZBX-9522.local-storage.patch    
Issue Links:
Causes
causes ZBX-16491 Javascript error in local storage syn... Closed
Duplicate
Sub-task
depends on ZBX-15870 Zabbix version number should not be a... Closed
depends on ZBX-15871 Frontend messaging("RESOLVED") is sti... Closed
depends on ZBX-15888 Frontend messaging audio should be su... Closed
part of ZBXNEXT-5235 Notification should describe problem ... Open
Team: Team B
Sprint: Sprint 55 (Aug 2019), Sprint 49 (Feb 2019), Sprint 50 (Mar 2019), Sprint 51 (Apr 2019), Sprint 52 (May 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019)
Story Points: 30

 Description   

Using configurations below:

  • "User Profile" => "Message timeout (seconds)": 60 sec
  • "User Profile" => "Refresh (in seconds)": 1 sec

On "Monitoring" => "Latest data" screen, frontend messaging popoup appeared as configurations above. However, there are some unexpected behaviour on "Monirtoing" => "Dashboard" screen.

  • messaging popup appears 40 - 50 sec later
  • popup doesn't hide automatically

Changing "Refresh time in seconds" configuration on each cell of dashboard didn't affect.

Forced-reload of browser show/hide popup correctly, so It seems that there's a problem in refresh behaviour on dashboard screen.

 Comments   
Comment by Oleksii Zagorskyi [ 2015 Apr 28 ]

Take into account recently fixed ZBX-9367
Also, recently in ZBX-9366 we clarified in doc that dashboard doesn't actually use the Refresh from user profile.

I think you need to reconsider issue description after reading those two issues.

Comment by Kazuo Ito [ 2015 Apr 28 ]

getServerMessages function of class.cmessages.js is running at 60-second intervals.
Therefore, display the alert on Dashboard screen and Configuration screen.

In addition, the time to display the alert is extremely short.
Time until the hide is being calculated from the time that the event has occurred?

I hope to display the time alert specified in the "Message timeout (seconds)".

Comment by Kodai Terashima [ 2015 Apr 30 ]

I seems that Frontend messaging shows popup:

  • by refresh screen
  • every 60 sec, by getServerMessages()

So Frontend messageing popups even if "users' profile => refresh" configuration doesn't affect dashboard.
However, the problem is, sometime popup doesn't appear or hide immediately because popup closing time is calculated by server side "event time + Message timeout (seconds)".

For example if Messaging timeout is 60sec (default):

  • 00:00 -> Problem event happens
  • 00:50 -> popup appears by getServerMessage
  • 01:00 -> popup disappear because "hiding time" is defined by server "00:00 + 60sec"

In this case user can see popup only 10 sec. I think it's better to change the period calculation to "now + Massaging timeout".

Comment by Oleksii Zagorskyi [ 2015 Apr 30 ]

I never used and investigated global messaging before.
Indeed, getting frontend messages interval is hardcoded to 60 seconds.

I was able to reproduce missing messages if an event generated more than [Message timeout] seconds before the frontend gets messages.
I configured not default 10-30 seconds for "Message timeout"

In other words global messaging are not guaranteed to be displayed.
We should not allow such user configuration.

I wonder why for a global warning "Zabbix server is down" we use hadcoded 10 seconds but for the global messaging much bigger 60 seconds.
Vice versa would be more logical, IMO.

Comment by Marc [ 2015 Jul 29 ]

zalex_ua,
Could it be because the TCP socket check is expected to be less extensive as the respective API call?

Oh, I'm so sorry. Just noticed that I answered to a quite old comment. I'd should rather get a coffee first before doing anything else

Comment by Marcelo de Borba [ 2018 Jul 30 ]

I'm with same problem here, after 4.0 upgrade.

Comment by Mārtiņš Tālbergs (Inactive) [ 2019 Mar 18 ]

IMPLEMENTED in development branch feature/ZBX-9522-4.0

Unofficial 3.0 patch prepared in development branch feature/ZBX-9522

Comment by Mārtiņš Tālbergs (Inactive) [ 2019 May 22 ]

Since Zabbix 3.0 and 3.4 supports IE9 and IE10, we cannot implement this messaging in Zabbix versions lesser than 4.0. We do provide ZBX-9522-3.0.tar.gz. Implementation will be released from Zabbix 4.0. If you are using the provided patch with Zabbix 3.0 - be aware to use web browsers that are supported in Zabbix 4.0.

UPDATE [28-05-2019]:

Fixed problem notification and its resolved notification being displayed simultaneously in ZBX-9522-3.0.v2.tar.gz.
 

Comment by Alexander Vladishev [ 2019 Aug 23 ]

Updated documentation:

Generated at Tue Apr 23 16:40:46 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.