Outgoing Email Settings

Configures the settings for email notifications by MySQL Enterprise Service Manager. You must configure the From Address SMTP Server settings. If your server requires authorization, complete the necessary server login details, and whether SSL is required.

You can test your configuration immediately by adding an email address to the On Save, Send Test Email Message to box.

For more information about Outgoing Email Settings see, Section 15.3.2.7.5, “Outgoing Email Settings”.

SNMP Traps

The SNMP Traps section of the Global Settings tab allows you to enable Simple Network Management Protocol so that your Network Management System (NMS) can handle events created by the MySQL Enterprise Monitor. SNMP notifications are off by default. You can enable them by clicking the Enable SNMP Notifications checkbox.

MySQL Enterprise Service Manager includes support for both SNMPv1 and SNMPv2. You can select the SNMP version to use by clicking the corresponding Use SNMPv1 or Use SNMPv2 radio button.

In the Target 1 or Target 2 text box enter the IP address or hostnames of your NMS listeners. The port number defaults to the well-known SNMP port, 162. If you are not using this port, enter the port that your Network Management System is listening on.

Enter the appropriate community string in the Community String text box. The default value for this string is public.

For the trap address for Advisor traps, you can optionally elect to use the address of the agent that triggered the alert, rather than the address of the MySQL Enterprise Service Manager. To do this, click the Use the remote MySQL agent host IP address as the SNMP trap agent address for Advisor traps. For internally generated SNMP traps (i.e. with MySQL Enterprise Service Manager) you can also specify an alternate address by putting the IP address in the SNMP trap agent address for internally generated traps box.

To ensure that the target you have specified is valid, check the On Save, Send Test Trap check box. The remaining check boxes help you to configure how your NMS responds to MySQL Enterprise Monitor. Check the Up/Down Application check box to configure NMS for starting up or shutting down the MySQL Enterprise Monitor. For configuration of advisor events choose a level of severity and check the Advisor event with the severity of Critical check box. Finally, choose the Application Error check box to configure NMS to support application error traps. Be sure to save your settings before exiting.

If you wish to enable SNMP traps globally, check the Enable SNMP Notifications checkbox. To enable SNMP traps only for specific rules run against specific servers or server groups leave this checkbox unchecked — enabling specific SNMP traps is done as rules are scheduled. For instructions on doing this see Section 15.7.2, “Scheduling Rules”.

The Management Information Base (MIB) file associated with SNMP trapping is called MONITOR.MIB. For the location this file see The Management Information Base (MIB) File.

Server Locale

The Server Locale setting determines the language of notification for the following items:

The initial value in this drop down list box is the locale for the OS on which the Dashboard is running.

Server Hostname

You can alter the hostname and port used to identify the MySQL Enterprise Service Manager when reporting notifications. This can be useful if the server hostname, and the hostname you want to use when connecting to your MySQL Enterprise Service Manager

You can also alter the name for the server displayed in the login page by changing the value in the Login Display Name. You may want to use this to display an organizational or divisional title, rather than the hostname, of the MySQL Enterprise Service Manager.

Data Purge Behavior

The Data Purge Behavior section of the Global Preferences page lets you remove old log files and also old data from the repository. The default purge interval is never. If you wish to purge data, change this setting by choosing from the drop-down list. Choosing 52 weeks, for example, will remove all data that is older than a year.

You can configure the data purge behavior for a number of different systems individually:

Notes for setting purge behavior:

Remote Server Inventory Schedule

MySQL Enterprise Monitor keeps track of all the databases and tables in a server, as well as the amount of RAM, disk space, and other items. A re-inventory updates this information in case you have added or dropped databases and tables. Depending upon the configuration of your system, this operation can tax resources. If you are monitoring many remote servers this is an operation you may want to perform in off-peak hours only.

MySQL Enterprise Credentials

You can specify the credentials for logging into the MySQL Enterprise Website. These should match the user name and password that you have registered with MySQL for your enterprise subscription.

HTTP Proxy Settings

You may want to update your HTTP Proxy Settings if your MySQL Enterprise Service Manager is not directly connected to the internet. The proxy settings will be used when updating the information within the What's New page and when accessing the MySQL Enterprise Website for authentication of your license and product key information. For more information, see Section 15.6, “The What's New Page”.

MySQL Enterprise Product Key

You may update your MySQL Enterprise Product Key. If you do not have access to the Internet from the Dashboard, this provides an alternate way to update or activate the MySQL Enterprise Monitor.

To enter your product key first download it from the MySQL Enterprise website. Copy the key to a location accessible from the Dashboard. Use the Browse button to locate the key and then press the save button.

If you wish to switch from using your MySQL Enterprise credentials to using a product key to update MySQL Enterprise Monitor, you must first clear your credentials. Do this by removing the email address from the MySQL Enterprise Credentials section and then clicking the save button. You may then enter and save your MySQL Enterprise product key.

Advisor Bundle

You can update your Advisor Bundle and the associated rules and graphs by importing a new Advisor Bundle. To update your Advisor Bundle using a bundle file that you have previous downloaded:

To update the Advisor Bundle automatically from the MySQL Enterprise Website using your existing MySQL Enterprise Credentials, click on the update advisors button.