MySQL Bugs: #49225: Server stopped, but WB server health graphs say differently

Bug #49225	Server stopped, but WB server health graphs say differently
Submitted:	30 Nov 2009 18:32	Modified:	8 Dec 2009 13:50
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2 r4643	OS:	Windows (XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	badprio

Description:
I used WB to stop my server.  This caused changes in the server health graphs, but they still show 2 active connections, 6K/s traffic, and 55% key efficiency.

How to repeat:
Stop monitored server.

Suggested fix:
Clearly disable server health graphs when server is stopped (or inaccessible).

Server health graphs

Attachment: SP32-20091130-102845.gif (image/gif, text), 91.72 KiB.

The status widgets need some flag to tell them they're disabled. In that state they should perhaps
be rendered in low saturation red with N/A written on top or something.

This is not a P2, however.

It is a P2 if the product is telling a user that their production database is running, when it is not.  That's a critical component of monitoring, and since WB is exposing this information, it cannot afford to mislead users into believing that system is available when it is not.

The only reason I would not classify this as P1 is because, on the same line, there is indication that the server is unavailable.  It is still misleading and conflicting information, and needs to be resolved pre-GA, IMHO.

Fixed in 5.2

fixed in repository. when no data is received from server, red indicators are displayed within the graphs informing user.
will be included in 5.2.11

An entry has been added to the 5.2.11 changelog:

Even though the server had been stopped, the Server Status graphical panel displayed values for active connections, traffic and key efficiency, giving the impression that the server was still active.

Hey everyone, hope you are doing well! Just wanted to share my thoughts and experiences involving this bug. I encountered a situation where I used WB to stop my server, but interestingly, the server health graphs continued to display data that suggested the server was still active. It showed two active connections, 6K/s traffic, and 50% key efficiency, despite the server being stopped.

In my opinion, this is quite puzzling and can lead to confusion for users relying on accurate server health information. It seems like a clear solution would be to disable or hide the server health graphs when the server is stopped or inaccessible. By doing so, it would prevent any misleading data from being displayed and provide users with accurate information about the server's status.

For those interested in diving deeper into this issue, you can check this source: https://andersenlab.de/industries/healthcare
I believe sharing our emotions and knowledge on this topic can help foster a more collaborative and effective approach to problem-solving.