MySQL Bugs: #53579: Consolidated diagram of MEM components

Bug #53579	Consolidated diagram of MEM components
Submitted:	11 May 2010 17:31	Modified:	25 May 2012 6:36
Reporter:	Lig Isler-Turmelle	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Documentation	Severity:	S4 (Feature request)
Version:	2.2.0.1709	OS:	Any
Assigned to:	Philip Olson	CPU Architecture:	Any
Tags:	regression

Description:
The 2.2 documentation has a few diagrams of the structure of MEM but there is no single cohesive image of MEM and it's individual parts and components. (https://enterprise.mysql.com/docs/monitor/2.2/en/mem-introduction.html)

Where do the users come in, where does the client applications come in, whre/how does the agent talk to the proxy, where do the connectors come in, what ports are used by MEM and which direction should they be open, etc.

For a visual learner a picture can be clearer then an entire chapter.

How to repeat:
na

Suggested fix:
create the image and add it to the documentation

Thank you for the documentation request.

There are a number of reasons why I chose not to include a single big diagram of everything involved in MEM. The main one is simply complexity - there are so many different components to display, and describe, and differentiate on screen that the whole thing could become a mess.

The second reason is that there are a number of different possible configurations and layouts, and we don't want to suggest that all of these items have to be connected, or that everything has to be configured in exactly the way we've shown it in our big diagram. There are people who will not use QA, and ergo not be interested in the proxy, or who wont use the connectors to provide QA information. There will also be those monitoring local servers and remote servers, those monitoring replication setups (in various different structures) and those monitoring multiple combinations of all of the above with, and without, QA, replication topology discovery, and applications directly attached to each monitored MySQL server.

Trying to represent this in a single diagram would be confusing at best, and simply unusable at worst. Trying to show this in multiple different diagrams with all of the different combinations would be equally confusing.

That is why (with discussion with Leith) we went for a simpler model of describing a basic overall structure, and then providing examples of specific scenarios and connections between different areas of the components. This enables us to show different combinations and deployments, and to show specific areas and layouts of the different components.

If you have specific scenarios and examples that you want to see, or problems with the specific diagrams already there, I would suggest you provide more information.

Nicer diagrams is a general wishlist item all around, but not on the MEM front burner right now.

This exists here:
http://dev.mysql.com/doc/mysql-monitor/2.3/en/mem-qanal-using-feeding.html