安装MySQL Enterprise Monitor
对于MySQL的监控工具，市面上有很多种，这里介绍怎么安装MySQL Enterprise Monitor，官方提供的工具，安装记录不详细解释，记录如下:
[root@ora11g soft]# ./mysqlmonitor-3.0.22.3178-linux-x86_64-installer.bin
Language Selection
Please select the installation language
[1] English - English
[2] Japanese - ―￥èa
Please choose an option [1] : 1
Info: During the installation process you will be asked to enter usernames and
passwords for various pieces of the Enterprise Monitor. Please be sure to make
note of these in a secure location so you can recover them in case they are
forgotten.
Press [Enter] to continue :
----------------------------------------------------------------------------
Welcome to the setup wizard for the MySQL Enterprise Monitor
----------------------------------------------------------------------------
Please specify the directory where the MySQL Enterprise Monitor will be
installed
Installation directory [/opt/mysql/enterprise/monitor]:
----------------------------------------------------------------------------
Select Requirements
Select Requirements
Please indicate the scope of monitoring this installation will initially encompass so we can configure Tomcat and MySQL memory usage accordingly. The manual contains instructions for updating the configuration later, if needed. This installation will monitor a:
System Size
[1] Small system: No more than 5 to 10 MySQL Servers monitored from a laptop computer or low-end server with no more than 4 GB of RAM
[2] Medium system: Up to 100 MySQL Servers monitored from a medium-size but shared server with 4 GB to 8 GB of RAM
[3] Large system: More than 100 MySQL Servers monitored from a high-end server dedicated to MEM with more than 8 GB RAM
Please choose an option [2] : 2
----------------------------------------------------------------------------
Tomcat Server Options
Please specify the following parameters for the bundled Tomcat Server
Tomcat Server Port [18080]:
Tomcat SSL Port [18443]:
----------------------------------------------------------------------------
Service Manager User Account
You are installing as root, but it's not good practice for the Service Manager
to run under the root user account. Please specify the name of a user account
to use for the Service Manager below. Note that this user account will be
created for you if it doesn't already exist.
User Account [mysqlmem]: mysql
----------------------------------------------------------------------------
Database Installation
Please select which database configuration you wish to use
[1] I wish to use the bundled MySQL database
[2] I wish to use an existing MySQL database *
Please choose an option [1] : 2
* We will validate the version of your existing MySQL database server during the
installation. See documentation for minimum version requirements.
Important: MySQL Enterprise Monitor 2.3 and 3.0 cannot share a Repository. If
you're not using the bundled Repository and will be running both versions in
your environment, you must set up and maintain separate repositories for them.
Visit the following URL for more information:
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-install-server.html
----------------------------------------------------------------------------
Repository Configuration
Please specify the following parameters for the existing MySQL server
Repository Username [service_manager]: root
Password :
Re-enter :
MySQL Hostname or IP address [localhost]:
MySQL Database Port [3306]:
MySQL Database Name [mem]:
Use SSL when connecting to the database [y/N]: y
Warning: SSL is not enabled in the existing MySQL server. Please either uncheck
the SSL option or manually enable SSL in the MySQL server before continuing.
Press [Enter] to continue :
----------------------------------------------------------------------------
Repository Configuration
Please specify the following parameters for the existing MySQL server
Repository Username [root]:
Password :
Re-enter :
MySQL Hostname or IP address [localhost]:
MySQL Database Port [3306]:
MySQL Database Name [mem]: kevin
Use SSL when connecting to the database [Y/n]: n
----------------------------------------------------------------------------
Setup is now ready to install MySQL Enterprise Monitor on your computer.
Do you want to continue? [Y/n]:
----------------------------------------------------------------------------
Please wait while Setup installs MySQL Enterprise Monitor on your computer.
Installing
0% ______________ 50% ______________ 100%
#########################################
----------------------------------------------------------------------------
Completed installing files
Setup has completed installing the MySQL Enterprise Monitor files on your
computer (errors were found during the installation process).
Uninstalling the MySQL Enterprise Monitor files can be done by invoking:
/opt/mysql/enterprise/monitor/uninstall
To complete the installation, launch the MySQL Enterprise Monitor UI and
complete the initial setup. Refer to the readme file for additional information
and a list of known issues.
Press [Enter] to continue :
----------------------------------------------------------------------------
Completed installing files
WARNING: To improve security, all communication with the Service Manager uses
SSL. Because only a basic self-signed security certificate is included when the
Service Manager is installed, it is likely that your browser will display a
warning about an untrusted connection. Please either install your own
certificate or add a security exception for the Service Manager URL to your
browser. See the documentation for more information.
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-install-server.html
Press [Enter] to continue :
----------------------------------------------------------------------------
Setup has finished installing MySQL Enterprise Monitor on your computer.
View Readme File [Y/n]:
README
MySQL Enterprise Monitor - http://www.mysql.com/monitoring
----------------------------------------------------------------------
Version 3.0.22.3178
----------------------------------------------------------------------
This is a release of MySQL Enterprise Monitor. For the avoidance of
doubt, this particular copy of the software is released under a
commercial license and the GNU General Public License does not apply.
MySQL Enterprise Monitor is brought to you by Oracle.
Copyright (c) 2005, 2015, Oracle and/or its affiliates. All rights
reserved.
This distribution may include materials developed by third parties.
For license and attribution notices for these materials, please refer
to the documentation that accompanies this distribution (see the
"Licenses for Third-Party Components" appendix) or view the online
documentation at:
http://dev.mysql.com/doc/mysql-monitor/3.0/en/index.html.
Welcome to the MySQL Enterprise Monitor. This README file contains
the following sections:
Press [Enter] to continue :
GETTING STARTED
IMPORTANT INSTALL & CONFIGURATION CHANGES FROM EARLIER VERSIONS
INSTALLATION
UPGRADE NOTES
REPORTING ISSUES & FEEDBACK
For more information about the MySQL Enterprise Monitor (MEM), refer
to the helpful tooltips in the MEM UI, or read the complete
documentation that can be downloaded from the same place you
downloaded the package containing this README file, or read the
documentation online at:
http://dev.mysql.com/doc/mysql-monitor/3.0/en/index.html
----------------------------------------------------------------------
GETTING STARTED
----------------------------------------------------------------------
IMPORTANT: If you're performing an upgrade, make sure to read the
complete documentation for important guidance on doing so safely.
If you're doing a new installation, here are basic steps:
Press [Enter] to continue :
(1) Download, install and launch the Service Manager
(2) Open the UI in your browser
(3) Complete configuration using the UI's first-time setup screen
(4) Install one Agent on each additional Host you will monitor
(optional, but highly recommended)
If you will be monitoring a large number of hosts and/or MySQL
Instances, see the complete documentation for guidance on tuning Agent
and Service Manager settings.
----------------------------------------------------------------------
IMPORTANT INSTALL & CONFIGURATION CHANGES FROM EARLIER VERSIONS
----------------------------------------------------------------------
We recommend installing a single Agent on each host system you wish to
monitor. New in this release, a newly-installed Agent will begin
collecting local CPU, memory, file system, and other OS-related data
whether or not the Agent has also been configured to monitor a MySQL
Instance at install time. The Agent will also look for running MySQL
processes and report them as unmonitored in the UI. You can ignore or
add monitoring connections to them on the MySQL Instances Dashboard.
(Process discovery is not currently supported on Windows.)
Press [Enter] to continue :
The Service Manager now includes a built-in Agent that automatically
collects OS-related data (including unmonitored MySQL processes) from
its own host and also monitors the MySQL Repository that MEM uses to
store data it collects from your monitored systems.
In another change from earlier versions, we strongly recommend
installing only one Agent per host with this release regardless of how
many MySQL Instances you have running on that host. To conserve
resources on monitored hosts, the 3.0 Agent is, by default, configured
to monitor approximately 5-10 MySQL Instances (actual number varies
with system load and performance). See the complete documentation for
guidance on tuning the Agent's settings, allowing it to monitor many
additional instances of MySQL.
Finally, note that SSL is now required as follows:
* HTTP requests to the 3.0 UI now redirect to a secure port (and may
generate an "untrusted site" warning in your browser, see complete
documentation for details).
* 3.0 Agents always use a secure connection when communicating with
the Service Manager. For backwards compatibility, SSL is still
optional (but recommended) for 2.3 Agents connecting to the 3.0
Press [Enter] to continue :
Service Manager.
----------------------------------------------------------------------
INSTALLATION
----------------------------------------------------------------------
WARNING - Before you install:
* Make sure to retain and securely store a written copy of all login
credentials that you specify throughout the installation and
configuration process. For security reasons, there is no way to
recover forgotten passwords, and the configuration reports no longer
include credential information.
* MEM stores data it collects from your monitored systems in a MySQL
database instance ("Repository"). The Service Manager installer will
optionally install and manage its own "Bundled" Repository, or you
can direct the installer to utilize a MySQL Instance you already
maintain. MEM 3.0 and earlier versions *cannot* share a common
Repository; if you're not using the bundled Repository and will be
running MEM 3.0 in parallel with an earlier version, set up and
maintain separate Repositories for each of them. (See the complete
documentation for more information, including minimum MySQL
version managing the Repository.)
Press [Enter] to continue :
* Refer to the complete documentation if you're performing an upgrade.
Service Manager:
----------------
Execute the MEM Service Manager Installer that you downloaded from
oracle.com and follow the prompts.
After the Installer exits, load the UI to complete the installation
and initial configuration process. If you installed on localhost using
the default ports, the URL to the UI would look like this:
https://localhost:18443/Setup.action
You will use the Manager credentials you specify here to login to the
UI and will provide the Agent user and password when you install
additional Agents.
Agent:
------
Several differences from the 2.3 Agent installation are worth noting
(see the documentation for more details):
Press [Enter] to continue :
- Multiple MySQL user accounts with different privilege levels
(Admin, General, Limited) are now defined and used by the Agent
- Groups play a central role in the new UI and can optionally be
assigned at Agent install-time
- The old Agent .ini files (mysql-monitor-agent.ini and
agent-instance.ini) are no longer supported
- Passwords in the .ini file are now stored in encrypted form
- The Service Manager now includes a built-in Agent (described above)
- The MySQL Proxy and Aggregator are no longer bundled with the
Agent installer. See the complete documentation for guidance if
you will continue to use them with MEM 3.0.
Performance Tuning MEM for your environment
-------------------------------------------
Customizing Tomcat and MySQL configuration can make a dramatic
difference to MEM's performance. Consult the complete documentation
for more information.
Consult the Troubleshooting sections of the online documentation if
any of these occur:
- You have trouble starting your Agent
- The Agent starts but doesn't show up in the UI
Press [Enter] to continue :
- You're using the Query Analyzer but no results are shown on the
Query Analyzer page (wait at least 10 minutes after startup)
Contact Support at https://support.oracle.com/ if you have problems
or need help tuning MEM for your environment.
If you are upgrading from a previous version, see the UPGRADE NOTES
below.
Note that the source code for the LGPL components used in the Service
Manager can be found in the licenses/lpgl directory.
----------------------------------------------------------------------
UPGRADE NOTES
----------------------------------------------------------------------
WARNING! MySQL Enterprise Monitor 3.0 has entirely different
inventory, instrument data, Query Analyzer, Advisor configuration, and
notification models from 2.3. Consider installing 3.0 in parallel with
your production 2.3 system instead of performing an upgrade. History
data for Events, Graphs, Query Analysis, and configuration data for
Advisor schedules are not migrated.
Press [Enter] to continue :
Before you attempt an upgrade, make sure to see the guidance provided
in the complete documentation with this package or go to:
http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-upgrading-3.0.html
We strongly recommend that you backup your existing Repository before
proceeding with an upgrade. If you are not using the bundled
Repository, back up your self-managed Repository data prior to running
the update installer on the Service Manager. Depending on the size of
your Repository, a backup can take a lot of time and disk space. See
"Backing up MySQL Enterprise Service Manager" in the complete
documentation for details.
----------------------------------------------------------------------
REPORTING ISSUES & FEEDBACK
----------------------------------------------------------------------
To report a problem, get help with an issue or provide product
feedback, login to https://support.oracle.com/. Generally, it's
better to create a separate issue for each problem you're reporting.
Do not hesitate to file a Support issue if you need help tuning MEM to
Press [Enter] to continue :
monitor a large number of hosts and MySQL instances.
If you'd like to participate in a future beta test of MEM, contact
Support, your Sales Representative or your Sales Engineer.
Thanks and Happy Monitoring!
- The MySQL Enterprise Tools Development Team
Copyright ? 2005, 2015, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license
agreement containing restrictions on use and disclosure and are
protected by intellectual property laws. Except as expressly permitted
in your license agreement or allowed by law, you may not use, copy,
reproduce, translate, broadcast, modify, license, transmit,
distribute, exhibit, perform, publish, or display any part, in any
form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for
interoperability, is prohibited.
If this software or related documentation is delivered to the U.S.
Government or anyone licensing it on behalf of the U.S. Government,
Press [Enter] to continue :
the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related
documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical
data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use,
duplication, disclosure, modification, and adaptation shall be subject
to the restrictions and license terms set forth in the applicable
Government contract, and, to the extent applicable by the terms of the
Government contract, the additional rights set forth in FAR 52.227-19,
Commercial Computer Software License (December 2007). Oracle USA,
Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information
management applications. It is not developed or intended for use in
any inherently dangerous applications, including applications which
may create a risk of personal injury. If you use this software in
dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to
ensure the safe use of this software. Oracle Corporation and its
affiliates disclaim any liability for any damages caused by use of
this software in dangerous applications.
Press [Enter] to continue :
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information
on content, products, and services from third parties. Oracle
Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party
content, products, and services. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due
to your access to or use of third-party content, products, or
services.
Press [Enter] to continue :
Info: To configure the MySQL Enterprise Monitor please visit the following page:
https://localhost:18443
Press [Enter] to continue :
[root@ora11g soft]#