MySQL Enterprise Monitor 3.0 Manual  /  ...  /  MySQL Enterprise Monitor Limitations

C.1 MySQL Enterprise Monitor Limitations

The following items are known limitations within MySQL Enterprise Monitor:

  • The maximum size for each data item stored within the mysql.inventory table is 64 bytes.

  • Fonts used for MySQL Enterprise Service Manager graphs might not be displayed properly if a required font is missing.

    To specify a custom font, set a custom property within the embedded MySQL Server to a known working font. Connect to your embedded MySQL Server using the information provided by the configuration_report.txt file. Once connected, execute the following statement:

    mysql> INSERT INTO map_entries VALUES (1,'Helvetica','graph.font');

    Replacing Helvetica with the font to use.

    The font used for graph rendering is selected as follows, in this order:

    1. The user override value.

    2. The MySQL Enterprise Service Manager default of Arial.

    3. The graph engine default of SansSerif.

  • You cannot monitor more than one MySQL Enterprise Monitor User Interface instance hosted on the same machine simultaneously within the same browser, even if each MySQL Enterprise Monitor User Interface uses a different port for access. The effect of this limitation can be more significant on certain browsers.

  • When monitoring multiple MySQL instances with one MySQL Enterprise Monitor Agent, if any of the MySQL instances are down when the agent is started, the agent does not attempt to reconnect to the servers. This could lead to indications that MySQL instances were down when in fact they were running and available. To avoid this problem, ensure all of the monitored instances are available before starting the agent.

  • The query length available for Query Analysis is limited, depending on the source. For example, a query that exceeds the limit is truncated and only displays part of the query in the "Example" section of the query analysis report.

    With 3.0 Agents: When using the Performance Schema as a source, queries are limited to the digested Performance Schema limit of 1,024 characters.

    With 3.0 Agents: When not using the Performance Schema as a source, the limits are set by the source of the data, if there is a limit at all.

User Comments
Sign Up Login You must be logged in to post a comment.