Documentation Home
MySQL Enterprise Monitor 3.4 Manual
Related Documentation Download this Manual

7.1 General Considerations

This section describes some of the general tasks which may be required after installation or upgrade.

New Users

  1. Groups and Connections: Groups have always been used to define Event handling and Advisor scheduling policies; in this release Groups can also be used to restrict visibility and access to specific MySQL instances and their hosts. Before you create Connections and set up Groups, we recommend you first read the note immediately following on Users, Roles, and Access Control

    • To create a Connection, select MySQL Instances from the Dashboard menu. Create new monitoring connections either by processing the unmonitored instances already discovered by MEM or by manually specifying connection parameters for each MySQL Instance you want to monitor. See Section 16.2, “MySQL Instance Details” for more information on creating connections in the User Interface.

    • Use the new Group Editor on the Settings menu to collect your MySQL instances into Groups.

  2. Users, Roles, and Access Control (ACLs): Before using the Settings menu to create User accounts, see Chapter 25, Access Control and Chapter 26, Access Control - Best Practices.

    Do you want to provide open access to all monitored resources for all Users? Or define Roles granting access to specific groups of MySQL Instances? If you intend to restrict access in this way, you must first create Groups of MySQL instances, see Chapter 17, Managing Groups of Instances. Only after you create groups can you create group-specific Roles.

    Finally, assign users to your Roles.

    You can also map users to Roles defined in LDAP or Active Directory.

  3. Configure Event Handling and Notification policies: Open Event Handling from the Settings menu. Complete, and test, the SMTP, or SNMP, configuration. See Chapter 22, Events and Event Handlers for more information.

  4. Overview Dashboard: Select Overview from the Dashboard menu. Set the defaults for the groups you want to view, the time range, and graphs to display. See Chapter 15, Overview for more information.

  5. Replication Dashboard: If you are using MySQL Replication, select the Dashboards menu, click on Replication and select a group to view its topology, configuration, status and replication error details. See Chapter 19, Replication Dashboard for more information.

  6. Advisors: You can accept the defaults defined, or select Advisors from the Settings menu and customize the threshold for groups, or individual MySQL Instances. For more information, see Chapter 21, Advisors.

  7. SQL Performance Tuning - If you are monitoring instances of MySQL running version 5.6.14 or later, rich SQL performance tuning data is available in the Query Analyzer. (If you are monitoring earlier MySQL versions, make sure to download a Query Analyzer plug-in so you can see SQL performance data as well.)

  8. I/O and Lock Contention - If you are using MySQL 5.6 or later consider deploying the sys schema, and making use of the new Database File I/O and Lock Waits reports from the Reports & Graphs menu. These help you identify who or what is using the most I/O, and whether there is any lock wait contention within your MySQL Instance. See Section 20.2, “Database File I/O and Lock Waits” for more information.

Existing users: Guide to completing your upgrade

  • Update Agents: If you have not done so already, we recommend updating your Agents before continuing. See Chapter 6, Upgrading MySQL Enterprise Monitor Installations.

  • Users, Roles, and Access Control (ACLs): This release introduces Access Control Lists (ACLs). Built-in Roles have replaced the privileges previously defined in Manage Users in version 3.0. Your system already has been migrated, however we strongly recommend reviewing Chapter 25, Access Control and Chapter 26, Access Control - Best Practices.

    You can continue to permit 3.0-style open access to all monitored resources for all Users who login; but you can now also define Roles that allow visibility and access to specific Groups of MySQL Instances and grant those Roles only to selected Users. If you’re using external services like LDAP or Active Directory, you can optionally map users to roles you’ve defined there.

    If intend to use ACLs to restrict visibility or access, we suggest you review your existing Groups with that in mind. The new Group Editor is located in the Settings menu. For an explanation of how privileges are migrated from earlier versions, see Section 25.6, “Default Users and Roles”.

  • Overview Dashboard: If you haven’t already done so, select the Dashboards menu, click on Overview and set defaults for which Group you want to view, the graph time range, and the set and order of Graphs to display. See Chapter 17, Managing Groups of Instances.

  • SQL Performance Tuning: If you are monitoring instances of MySQL running version 5.6.14 or later, make sure to see the rich SQL performance tuning data available in the Query Analyzer. (If you are monitoring earlier MySQL versions, make sure to download a Query Analyzer plug-in so you can see SQL performance data as well.)

  • I/O and Lock Contention: If you are using MySQL 5.6 or later consider deploying the sys schema, and making use of the new Database File I/O and Lock Waits reports from the Reports & Graphs menu. These help you identify who or what is using the most I/O, and whether there is any lock wait contention within your MySQL Instance. See tSection 20.2, “Database File I/O and Lock Waits” for more information.


User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.