Chapter 2 What's New in 3.1
Prev |  | Next

## Chapter 2 What's New in 3.1

This section provides a high-level overview of the differences between this release and its predecessor.

## 2.1 Security

### Access Control Lists

MySQL Enterprise Monitor 3.1 introduces Access Control List (ACL) support. MySQL Enterprise Monitor ACL enables the following:

- Define visibility: strictly limit access to specific groups of assets or grant access to all assets.

- Define Roles: rather than define permissions per user, as in previous releases, permission sets are defined in roles and multiple users can be assigned to each role. It is also possible to assign users to multiple different roles.

- Restrict access to sensitive data: grant or deny rights to view specific types of potentially sensitive data, such as Query Analyzer data.

- Authenticate using external services: map your users to roles defined in LDAP or Active Directory.

For more information, see Chapter 23, Access Control and Chapter 24, Access Control - Best Practices.

### MySQL Enterprise Firewall Monitoring

The MySQL Enterprise Firewall plugin hardens MySQL against threats such as SQL injection or attempts to exploit applications by using them outside of their legitimate query workload characteristics. MEM 3.1 notifies you if a potential security threat has been identified and provides pro-active configuration advice if your settings can be improved. View graphs of Access Denied, Access Granted and Suspicious Access counters over time for the MySQL instances you wish to safeguard. For more information on MySQL Enterprise Firewall, see MySQL Enterprise Firewall.

### MySQL Enterprise Audit Monitoring

Monitor and enforce MySQL Enterprise Audit configuration and usage across all of your MySQL servers. MEM 3.1’s policy-based Advisor and event-handling track and inform you about MySQL Enterprise Audit status (enabled/disabled), write waits, and lost events to help you ensure best practices and regulatory compliance. For more information on MySQL Enterprise Audit, see MySQL Enterprise Audit.

## 2.2 Performance Tuning

Identify I/O hot spots and lock wait contention in your application using the new Database File I/O and Lock Waits reports. These reports utilize `sys` schema which can be installed on the selected instance from within MySQL Enterprise Monitor. For more information, see Section 18.2, “Database File I/O and Lock Waits”.

Note

`sys` schema is supported on MySQL 5.6 and higher, only.

## 2.3 Usability

The following changes were made to the user interface.

- New and improved Group Editor available from the Settings menu.

- New User and Roles editor available from the Settings menu.

- Customizable graphs on the Overview dashboard.

- New File I/O and Lock Waits reports and graphs available from the Reports & Graphs page.

Prev | Up | Next
Chapter 1 MySQL Enterprise Monitor Introduction and Architecture | Home | Part II Installing MySQL Enterprise Monitor