Bug #34713 MySQL Enterprise Monitor documents have less enough error codes.
Submitted: 21 Feb 2008 3:09 Modified: 29 Jul 2008 15:06
Reporter: Mikiya Okuno Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Documentation Severity:S3 (Non-critical)
Version:1.3,2.0 OS:Any
Assigned to: MC Brown CPU Architecture:Any

[21 Feb 2008 3:09] Mikiya Okuno
There's a section named "Troubleshooting the Agent", but it only includes one error code E1031.

For troubleshooting purpose, it is not enough and the document should include all list of error codes and should explain what DBA should do when each error happens.

For example, what should DBA do when E1402 happens?

How to repeat:
[21 Feb 2008 5:20] Andy Bang
This seems somewhat important to me and may get lost as an S4 (Feature Request) bug, so I'm promoting it a small bit so Peter will see it and decide what to do.
[15 Mar 2008 11:18] Mark Leith
First step done, the docs are now auto-updated from the resources file that holds all of the E (server) error codes, along with the U (UI) codes that were already documented. 

A 1.3 manual has been split out as well as a part of this. 

Leaving this bug verified for now however, as there is still the question of resolution information being documented along with the error codes.
[19 Apr 2008 17:14] Andy Bang
Assigning to MC now that Peter is gone.