Bug #41631 server needs to show critical errors on the main page
Submitted: 19 Dec 2008 11:14 Modified: 9 Jan 2015 10:07
Reporter: Carsten Segieth Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Web Severity:S4 (Feature request)
Version:2.0.2.7126 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[19 Dec 2008 11:14] Carsten Segieth
Description:
Serious / critical problems should be shown on the main dashboard in a "good visible way".

Problem: my MEM server stopped working correct, no graphs were shown (all 6 had "Graph not available") and I started searching for the reason. The server was also extreme slow responding so I didn't wait for the Logs page to open.

I found the message

  org.hibernate.util.JDBCExceptionReporter
  Error
  19.12.2008 07:08:08
  The table 'dc_ng_long_now' is full

in the log after I had seen and fixed the disk space problem from the OS side.

It would have helped a lot to see such a message on the dashboard!

How to repeat:
let the MEM server run out of disk space

Suggested fix:
show this and similar critical messages on the dashboard. I see that not all "Errors" from the logs can be shown here, perhaps we have a list of critical situations that shall be shown there. I think also about any mail sending problems.