percona-agent Documentation

Transcription

1 percona-agent Documentation Release Percona June 30, 2015

2

3 Contents 1 Getting Started with Percona Cloud Tools How PCT Works Tools Quick Start Switching Organizations Using the Instance Tree Selecting Time Range Percona Agent Percona Agent Release Notes Percona Agent System Requirements Percona Agent Installation Guide Percona Agent Install Script Options Managing Percona Agent Instance Configuring Percona Agent Instance Query Analytics Setting Up Dashboards Query Profile Server Summary Query Details Reviewing Queries Performance Schema Other Reading Metrics Monitor Adding Charts Managing Chart Granularity Zooming and Synchronizing Disabling Updates Viewing Charts System Info Reports 25 7 Users and Organizations Account Settings Organization Membership i

4 7.3 User Roles API Key Security and Privacy 29 9 Frequently Asked Questions How to install Percona Agent on Amazon RDS? How to set up Percona Agent to use a proxy server? Which IP addresses does Percona Agent use? Does Percona Agent store data locally? What does write unix /var/lib/mysql/mysql.sock: broken pipe message mean? How to install Percona Agent on a server with old password authentication? Help and Support Community Support Percona Support Submitting Bugs Glossary 35 ii

5 Beta Disclaimer PCT (Percona Cloud Tools) is currently in beta. The following limitations apply: 3 organizations per user 5 agents per organization 8 days of data per agent Documentation is organizaed into sections according to features and components. The first section covers basic concepts and provides links to related material. Contents 1

6 2 Contents

7 CHAPTER 1 Getting Started with Percona Cloud Tools PCT is a hosted service that helps you manage MySQL performance. How PCT Works Tools Quick Start Switching Organizations Using the Instance Tree Selecting Time Range 1.1 How PCT Works Percona Agent collects performance data from a MySQL server, encrypts it, and sends to PCT through a secure websocket connection. Any members of your team can access the web application to analyse your data at cloud.percona.com using any browser that supports HTTPS (Hypertext Transfer Protocol Secure). 3

8 1.2 Tools PCT provides several tools for analysing collected data: Query Analytics aggregates MySQL query digest data to find performance problems. You can see a range of metrics for each individual query and run diagnostic queries to see execution details. Metrics Monitor enables you to set up dashboards with charts to monitor trends in MySQL and general system performance. You can drill down into problematic periods and compare metrics to see dependencies that might uncover the cause of problems. System Info provides a summary of information related to MySQL and system configuration. Reports are a way to get critical query digest data delivered to you regularly. 1.3 Quick Start If you have MySQL server running and configured correctly, you can start using PCT in three easy steps: 1. Create account Go to cloud.percona.com, create a PCT Account and log in. 2. Get your API key Get your API key at cloud.percona.com/api-key. 3. Install Percona Agent Log in to your MySQL server as root and run the following command: 4 Chapter 1. Getting Started with Percona Cloud Tools

9 $ curl -s bash /dev/stdin -api-key="<api key>" Check out this video to see how easy it is to get started For more information about installing Percona Agent, see the Installation Guide. 1.4 Switching Organizations When you register a PCT account, a default organization is created for you. You can use this default organization to get started. You can also create other organizations and be added to existing organizations. To switch between organizations, use the drop-down menu above the Instance Tree. For more information about organizations, see Users and Organizations. 1.5 Using the Instance Tree The Instance Tree is a hierarchical representation of your infrastructure, which corresponds to the currently selected organization. An OS instance represents a physical or virtual machine. An Agent instance represents a percona-agent service running on the machine. A MySQL instance represents a MySQL server on the machine. 1.6 Selecting Time Range PCT displays data collected during the time range selected in the Time Range menu. You can choose one of the predefined options (last hour, day, month, three months, year) or select a custom range Switching Organizations 5

10 6 Chapter 1. Getting Started with Percona Cloud Tools

11 CHAPTER 2 Percona Agent 2.1 Percona Agent Release Notes 2.2 Percona Agent System Requirements Supported Platforms Feature Matrix 2.3 Percona Agent Installation Guide Depending on your needs and preferences, the following installation types are available: Table 2.1: Installation Types Source Web Package (rpm, Repositories (cloud.percona.com) deb, tar.gz) (yum and apt) Uses curl Install script Package manager Automated 1 Yes (only) Yes (by default) Yes Manual/Interactive 2 No Yes Yes Slave 3 No Yes Yes Updates 4 No No Yes Web Install This is the fastest way to install the latest version of Percona Agent. A non-interactive installer is used, which attempts to configure everything automatically. 1. Get the API key at 2. Run the following command as root: $ curl -s bash /dev/stdin -api-key="<api key>" The installer attempts to automatically detect necessary MySQL options, as described in Percona Agent System Requirements. If it fails, the installed Percona Agent will not be able to collect any MySQL metrics and query data, only general system metrics. 7

12 For more control over the installation process, see Package Install Package Install Specific Version Package install can be used to install a specific version of Percona Agent, other than the latest. For this, select the required version from the drop-down list on the Download page. The Percona Agent distribution package contains an interactive install script that prompts the user for input when it is not able to detect necessary options. For example, the script prompts for the API key, unless you specify it using the -api-key option. 1. Download the archive with the latest Percona Agent distribution. 2. Extract the archive and change to the directory it creates. 3. Run the./install script as root. There are many options that you can pass to the install script for specific cases: Automated Install Slave Install Non-MySQL Install For a complete list of options, run the install script with the -help option or see the Install Script Options page. Automated Install To automate installation and disable install script prompts, use the -interactive=false option. In this case, installation will be the same as during a Quick Install _. Note: In this case, you have to specify the -api-key option. If the installer fails to detect necessary MySQL options, Percona Agent will not be able to collect MySQL metrics and query data, only general server metrics. To avoid this, you can pass necessary MySQL options to the install script, for example: $./install -interactive=false -api-key=1a2b3c -mysql-user=root -mysql-pass=pass -mysql-socket=/var/r Slave Install After you install Percona Agent on the master, run the install script with the -create-mysql-user=false option on the slave. In this case, the install script will prompt you for existing Percona Agent user credentials on MySQL. To install Percona Agent on the slave in automated mode, specify the agent s MySQL user credentials as options for the install script, for example: $./install -interactive=false -create-mysql-user=false -agent-mysql-user=name -agent-mysql-pass=pass Note: Specifying -agent-mysql-user automatically disables -create-mysql-user. 8 Chapter 2. Percona Agent

13 Non-MySQL Install If you want to install Percona Agent on a server without MySQL or you do not want to monitor a particular MySQL instance, pass the -mysql=false option to the install script: $./install -mysql=false In this case, Percona Agent will monitor only general server metrics Percona Software Repositories Percona provides repositories for popular package managers: yum (RPM packages for RedHat, CentOS, Amazon Linux AMI, etc.) apt (.deb packages for Debian, Ubuntu, etc.) You can use those package managers to install and update all Percona software with any dependencies. Installing on RPM-based systems To install Percona Agent using the yum manager: 1. Install an RPM that configures yum and installs the Percona GPG key: $ yum install Make sure that Percona packages are available from the repository: $ yum list grep percona 3. Install the Percona Agent package: $ yum install percona-agent Installing on Debian-based systems To install using the apt manager: 1. Add Percona package key to apt: $ apt-key adv --keyserver keys.gnupg.net --recv-keys 1C4CBDCDCD2EFD2A 2. Add Percona repository sources to /etc/apt/sources.list with the correct name of the distribution. For example, if you are running Ubuntu (Trusty Tahr), add the following lines: deb trusty main deb-src trusty main 3. Update local cache: $ apt-get update 4. Install the Percona Agent package: $ apt-get install percona-agent 2.3. Percona Agent Installation Guide 9

14 2.3.4 Updating Percona Agent When a new version of Percona Agent is available, use either Web Install or Package Install. The install script checks for the currently installed version and applies necessary updates. If you installed Percona Agent using a package manager, as described in Percona Software Repositories, then you can update it as follows: For yum, run the following command: $ yum update percona-agent Note: You can run the previous command without specifying the percona-agent package to make yum update all installed packages. For apt, run the following command: $ apt-get install --only-upgrade percona-agent Note: You can also run the following command, which installs the newest versions of all packages in your system: $ apt-get upgrade Uninstalling Percona Agent If you did a Web Install, run the following command: $ curl -s bash /dev/stdin -uninstall If you did a Package Install, change to the directory where the Percona Agent archive was extracted and run the following command: $./install -uninstall To drop the Percona Agent user from any MySQL instance that the agent was monitoring, execute the following: > DROP USER 'percona-agent'@'localhost'; > DROP USER 'percona-agent'@' '; To remove the agent s configuration and data from Percona Cloud Tools, log in and delete the agent at You can also delete any MySQL instances that the agent was monitoring at 10 Chapter 2. Percona Agent

15 2.4 Percona Agent Install Script Options 2.5 Managing Percona Agent Instance Real-time Status Online Logs Remote Control 2.6 Configuring Percona Agent Instance Percona Agent is a background service that collects performance data from a MySQL server. GitHub. Free You can freely deploy Percona Agent on any Linux host with one command. For more information, see the Percona Agent Installation Guide. Open-source Percona Agent source code is available on Secure Percona Agent encrypts collected data and communicates with PCT through a secure websocket connection. For more information, see Security and Privacy Percona Agent Install Script Options 11

16 12 Chapter 2. Percona Agent

17 CHAPTER 3 Query Analytics 3.1 Setting Up Dashboards The Query Analytics tool enables database administrators and application developers to analyze MySQL queries over periods of time and find performance problems. Query Analytics helps you optimize database performance by making sure that queries are executed as expected and within the shortest time possible. In case of problems, you can see which queries may be the cause and get detailed metrics for them. 3.2 Query Profile The Query Profile section provides a list of queries executed on the server in the specified period of time. It also shows valuable performance information about each query. The following screenshot shows an example of the Query Profile table: By default, the table lists ten queries with the highest total execution time. Use the Sort by field in the toolbar to change how queries are sorted: SUM Sort queries by total execution time (this is the default) MAX Sort queries by maximum execution time A box below the table shows the number of queries listed and the percentage of them compared to all queries. To show ten more queries in the table, click the button with the plus sign. The following information is available in the Query Profile table: 13

18 Rank Determined by the calculated load (see Load). Query The fingerprint of a query, where literal values are removed, whitespace normalized, etc. Similar queries with the same fingerprint are grouped together. Query ID Unique identifier of the query. Queries Number of times this query was executed during the selected period. QPS Average number of queries per second for the selected period. For example, INSERT metric_data was executed 34.7 million times during the last 24 hours (the previous example shows a one day period). If you divide 34.7 million queries by 86.4 thousand seconds, you get queries per second. Load Abstract measure of intensity for the query, calculated as the total time it took to execute all queries (see Total Time) divided by the actual time that passed. For example, INSERT metric_data was executed 34.7 million times during the last 24 hours with an average execution time of milliseconds (see Avg Time). This adds up to a total execution time of 1 day and 7 hours (31 hours). If you divide 31 hours by 24 hours that actually passed during the period, you get a load value of Load % Percentage of the load this query produced compared to the total load of all queries. For example, INSERT metric_data has a load value of 1.331, which is 20.52% out of the total load for all queries combined. Total Time Total time it took to execute all queries. Queries with the biggest total time are causing the most load. Avg Time Average time it took to execute one query, calculated as the total time divided by total number of queries. 95% The 95th percentile is the maximum time it took to execute 95% of queries. Only 5% of queries took more time to execute. This is an important measure of what the majority of users are experiencing. If the 95th percentile is low, then it is generally not a problem to see high values of maximum execution times (see Max Time) for only several queries. Max Time Maximum time it took to execute query. This may not be a good indicator of query performance, because it may have taken a long time to execute only several times out of millions during a specific period. You should use this value in combination with 95th percentile (see 95%). 3.3 Server Summary The Server Summary section provides a list of metrics for queries currently displayed in the Query Profile table. Some of these metrics are Query count, Query_time, Lock_time, Rows_sent, and so on. The following screenshot shows an example of the Server Summary table: The values depend on the units used by the specific metric. However, the columns in the table are the same for all metrics: 14 Chapter 3. Query Analytics

19 Total The count of whatever units are used by the metric. For Query_time, it is the total execution time of queries, for Rows_sent, it is the total rows in MySQL tables that were sent, and so on. Average The average of whatever units are used by the metric. For Query_time, it is the average execution time per query, for Rows_sent, it is the average rows in MySQL tables sent per query, and so on. Minimum The minimum of whatever units are used by the metric. For Query_time, it is the minimum execution time for a query, for Rows_sent, it is the minimum rows in MySQL tables sent by a query, and so on. 95% The 95th percentile of whatever units are used by the metric. It represents the maximum value for 95% of queries (it is lower for the remaining 5%). For Query_time, it is the maximum execution time for 95% of queries, for Rows_sent, it is the maximum amount of rows sent by 95% of queries, and so on. Maximum The maximum of whatever units are used by the metric. For Query_time, it is the maximum execution time for a query, for Rows_sent, it is the maximum rows in MySQL tables sent by a query, and so on Historical data for metric To see historical data for a metric, expand the metric. This opens a time graph with the Total values plotted above Average QPS. The following screenshot shows an example of the time graph for the Query_time metric: The previous example contains data for the last day in 10-minute periods. The time span and granularity depend on the Time range setting (for more information, see WebInterface). The Total graph shows the total time it took to execute queries for each 10-minute chunk. You can compare this to the global average queries per second. For example, in the previous screenshot, you can see how spikes in total execution time correspond to small drops in Average QPS. 3.4 Query Details The Query Details section opens in place of the Server Summary section when you select a specific query in the Query Profile table. This way you can drill down into data related to a particular query. In addition to the query name and checksum (unique identifier), the Query Details section provides the time and date when the query was first and last seen. It also contains a Metrics table similar to the Server Summary, as well as a Query Plan for the selected query Query Details 15

20 3.4.1 Real-time EXPLAIN and Table Info At the bottom of the Query Details section, you can see an example of the selected query. For information about how MySQL executes the query, run EXPLAIN on the query. For this, you can manually copy and paste the query to the server. PCT enables you to run EXPLAIN for the selected query directly from within PCT, and get a response in real time. Note: If you are using Percona Server 5.5 or earlier version, EXPLAIN is available only for SELECT queries due to server implementation. In case of Percona Server 5.6 and later versions, you can run EXPLAIN for UPGRADE, INSERT, and DELETE queries if you add necessary additional permissions to the Percona Agent user. You can also run Table Info for the selected query. This enables you to get SHOW CREATE TABLE, SHOW INDEX, and SHOW TABLE STATUS for each table used by the query directly from within PCT. 3.5 Reviewing Queries The Query Analytics tool enables you to review all database activities as you go through the details for various queries. When you select a query in the Query Profile table, you can use the buttons in the right part of the Query Details section to set the status for the query and categorize it using tags. You can then filter queries according to the assigned status and tags. At the bottom, you can add a comment for the query. This metadata is visible by all users in your organization, which enables collaboration for reviewing and tuning query performance. As you review queries, change the status accordingly: Not reviewed This is the default status. Reviewed Select this status after you review a query and there are no problems with it. Needs attention Select this status if a query requires deeper analysis or some other action associated with it. Query tags can be used by your team to categorize queries. Create your own set of tags, which corresponds to your procedures and environment. For example, one approach is to tag queries according to the different subsystems of your application, such as checkout or hotel-search. This will enable you to filter queries by meaningful actions performed by your users. 3.6 Performance Schema The default source of query data for Percona Cloud Tools is the slow query log. It is available in MySQL 5.1 and later versions. Starting from MySQL 5.6 (including Percona Server 5.6 and later), you can select to parse query data from the Performance Schema. Performance Schema is not as data-rich as the slow query log, but it has all the critical data and is generally faster. In some cases, it may be the only alternative. To use Performance Schema: 16 Chapter 3. Query Analytics

21 1. Enable it on the server by starting MySQL with the performance_schema variable set to ON. For example, use the following lines in my.cnf: [mysql] performance_schema=on Note: Performance Schema instrumentation is enabled by default on MySQL and later versions. 2. Configure Query Analytics to collect data from Performance Schema: (a) In the web UI, select Configure > MySQL. (b) Click Query Analytics for the MySQL instance you want. (c) Select Performance Schema in the Query Analytics Configuration dialog box. (d) Click Apply to save changes. For more information, see conf-qan. 3.7 Other Reading MySQL performance optimization: Don t guess! Measure with Percona Cloud Tools Measure the impact of MySQL configuration changes with Percona Cloud Tools PERFORMANCE_SCHEMA vs Slow Query Log 3.7. Other Reading 17

22 18 Chapter 3. Query Analytics

23 CHAPTER 4 Metrics Monitor The Metrics Monitor tool provides a historical view of metrics that are critical to the MySQL server. You can add charts related to MySQL performance on one dashboard, server availability metrics on another dashboard, and set up separate dashboards for different members in your team. Use the Dashboard drop-down list to select an existing dashboard, create a new dashboard, or remove a dashboard. Note: Use the Time Range menu to select the period of time, for which you would like to view metrics. Use the Host menu to select the host that you want to monitor. 4.1 Adding Charts A dashboard can be configured to contain several charts for various metrics. Although a chart can contain any number of metrics, do not overload it, unless you need to compare several metrics. Keep it simple and separate different types of metrics across charts. To add a chart to a dashboard: 1. Click Add chart. 2. Enter a name for the chart and a description. 3. Click Add new series. 4. Start typing the name of the metric and select the one you need from the drop-down list. Note: There are many metrics available, separated into types and subtypes using the forward slash (/). For example, metrics that begin with disk/ or memory/ are related to the general hardware and OS performance, while metrics related to MySQL begin with mysql/ and mysqlvar/. 19

24 5. Enter a custom description if necessary. 6. Select the type of the chart and the statistical value to be used. Note: The type and value depends on the metric and your needs. For example, you may want to see a bar chart of the count for created MySQL threads, and a line chart of the 95 percentile for MySQL query execution time. 7. Click OK to add the series. 8. If necessary, add other metrics to the chart. 9. Click Save to add the chart to the dashboard. 4.2 Managing Chart Granularity Percona Agent collects data every second, then aggregates it and updates charts every minute. You can select the granularity for charts using the Group menu, if you would like to group values differentely. Available grouping depends on the current time range. For example, if you are viewing data during last week you can select to group data points by 5 minutes, 1 hour, or 6 hours. This is useful for some metrics with high volatility. If frequent spikes are not as important as the overall trend, select a larger group to smooth out the chart. 4.3 Zooming and Synchronizing Charts are interactive, meaning that you can zoom in on a period of interest. For example, if you see a spike in throughput on a weekly chart, you can click and drag to select the period of time when the spike occured. By default, all charts in the dashboard are synchronized to update to the same period, and the corresponding custom time range is selected in the Time Range menu. Synchronization is useful to isolate events that occurred only during the period of interest. Sometimes, you may not want to synchronize all charts when zooming. To disable synchronization, click the Sync button in the Zoom field. Note: If you already zoomed in to a chart, you will not be able to disable synchronization until you reset the zoom. You have to click the Reset button, which appears in the Zoom field, then disable synchronization. If you want to keep synchronization for charts on the current dashboard, but do not want the Time Range menu to update to the corresponding custom time range, click the Metrics Configuration button in the far right corner and clear the Enable Zoom s time range globally check box. In this case, the global time range will remain when you open another dashboard. 20 Chapter 4. Metrics Monitor

25 4.4 Disabling Updates By default, charts are updated with new data every minute, and grouped according to the granularity selected in the Group menu. If you do not want to add new data to the charts, click Disable updates in the toolbar. For example, you may find a possible minor problem that you want to analyze later. You can disable chart updates, then come back to the problem, find the cause, fix it, and enable updates again to continue monitoring. 4.5 Viewing Charts Charts are arranged on a dashboard in the order they were added. Do not overload a dashboard with too many charts. If you have to scroll a lot, it may not be easy to find the chart you need. Besides, charts take time to load: the more charts you have, the greater lag you will experience when they are updated. When you hover over a chart, a popup is displayed with the current values. Also, a menu appears in the top part of the chart, which you can use to customize the appearence of the chart: Min/Max: Show the minimum and maximum values for a metric according to the selected granularity. For example, if values are grouped by hours, then in addition to the average value during that hour, the chart will also display the maximum and minimum values for that hour. 5/95 Pct: Show the 5 and 95 percentile values for a metric according to the selected granularity. For example, if values are grouped by hours, then in addition to the average value during that hour, the chart will also display the values below which 5 and 95 percent of observations during that hour fall. Toggle between linear and logarithmic scale. For example, if the values are too dense, switch to logarithmic scale. Toggle between line and dot chart 4.4. Disabling Updates 21

26 Edit the chart settings (these are initially configured when Adding Charts) Remove chart from dashboard The following screenshot shows an example of the MySQL Throughput metrics (number of queries and questions) on a line chart with a linear scale. The Min/Max and 5/95 Pct options are enabled. In the previous example, the mouse is hovered over April 11, 2015 at 13:00:00. The values correspond to the following: On average, there were MySQL queries per minute during the last hour 5 percent of observations during the last hour showed less than MySQL queries per minute 95 percent of observations during the last hour showed less than MySQL queries per minute The minimum amount of MySQL queries per minute during the last hour was 478 The maximum amount of MySQL queries per minute during the last hour was Chapter 4. Metrics Monitor

27 CHAPTER 5 System Info 23

28 24 Chapter 5. System Info

29 CHAPTER 6 Reports 25

30 26 Chapter 6. Reports

31 CHAPTER 7 Users and Organizations 7.1 Account Settings 7.2 Organization Membership 7.3 User Roles 7.4 API Key 27

32 28 Chapter 7. Users and Organizations

33 CHAPTER 8 Security and Privacy 29

34 30 Chapter 8. Security and Privacy

35 CHAPTER 9 Frequently Asked Questions How to install Percona Agent on Amazon RDS? How to set up Percona Agent to use a proxy server? Which IP addresses does Percona Agent use? Does Percona Agent store data locally? What does write unix /var/lib/mysql/mysql.sock: broken pipe message mean? How to install Percona Agent on a server with old password authentication? 9.1 How to install Percona Agent on Amazon RDS? This is currently not possible, because Percona Agent does not support monitoring multiple remote MySQL instances. It is a planned feature, which will be available soon. 9.2 How to set up Percona Agent to use a proxy server? Percona Agent does not support proxies. It is a planned feature, which will be available soon for HTTPS proxies. 9.3 Which IP addresses does Percona Agent use? Percona Agent communicates using the URI (uniform resource locator) specified by the link entry in /usr/local/percona/percona-agent/config/agent.conf. 9.4 Does Percona Agent store data locally? Percona Agent aggregates collected data in the /usr/local/percona/percona-agent/data folder. It usually reports collected data in regular intervals, but if there is a connection issue, this data is stored until the agent manages to send it. As of Percona Agent , the following limits apply to local data: 1 hour 10 MiB 31

36 100 files Previous versions did not limit the size of the data folder, which lead to situations when Percona Agent filled up disk space indefinitely. 9.5 What does write unix /var/lib/mysql/mysql.sock: broken pipe message mean? Messages in percona-agent.log are not necessarily from Percona Agent. This file is used to capture many various messages. You should refer to the agent log in the web UI for specific Percona Agent errors. To view the agent log, open Configure > Agent, and click info for the agent you want to troubleshoot. For more information, see Configuring Percona Agent Instance. This particular message is from the Go MySQL driver. It indicates a connection issue, and possibly a problem with credentials for the percona-agent user to access MySQL. First of all, make sure that there is a percona-agent user set up for the MySQL instance. If it is, try to restart the agent by running the following command: $ service percona-agent restart or $ /etc/init.d/percona-agent restart 9.6 How to install Percona Agent on a server with old password authentication? If you need to install Percona Agent on a server with old password authentication, specify the -old-passwords=true option. For MySQL 4.1 and later versions, you may have old passwords enabled explicitely. In this case, you can disable old passwords for one session while you install Percona Agent: mysql> SET SESSION old_passwords=0; Then create the percona-agent user and install Percona agent with the -create-mysql-user=false option. 32 Chapter 9. Frequently Asked Questions

37 CHAPTER 10 Help and Support 10.1 Community Support 10.2 Percona Support 10.3 Submitting Bugs 33

38 34 Chapter 10. Help and Support

39 CHAPTER 11 Glossary The following is a list of terms related to Percona Cloud Tools (PCT). API key A unique key used by Percona Agent to identify the data it collects as belonging to the corresponding organization. If you have a PCT Account, you can find the API key at Note: Make sure that the correct organization is selected. Metrics Monitor A tool used for presenting collected MySQL and system metrics on time-based charts. For more information, see the MetricsMonitor section. organization An entity in PCT that defines all infrustructure components and people involved. When you sign up for a PCT Account, a default organization is created. You can add other users to the organization, create other organizations, or be added to existing organizations. Each organization is assigned a unique API key, which is used by Percona Agent to identify the data it collects. During installation, Percona Agent adds corresponding server and MySQL instances to the organization. PCT Account A user account on cloud.percona.com. For more information, see the Account section. Percona Agent to PCT. A service that runs on the server, collects data about perfomance and MySQL metrics, and sends it For more information, see the Agent section. Percona Toolkit A collection of advanced command-line tools to perform a variety of MySQL and system tasks. The toolkit is used by Percona Agent to generate System Info reports. Performance Schema An alternative source of query data to the slow query log. Performance Schema is available starting from MySQL 5.6, and is enabled by default starting from MySQL Data is collected from the performance_schema.events_statements_summary_by_digest table, and is used by the Query Analytics tool. For more information, see Performance Schema. Query Analytics A tool used for analyzing the history of MySQL queries. Data is collected either using the slow query log or Performance Schema. For more information, see the QueryAnalytics section. slow query log The default source of query data for Query Analytics. Slow query log is available starting from MySQL 5.1, and provides a wealth of valuable data for deep analysis. A faster and more efficient way (but without as much data) is the Performance Schema. 35

40 System Info A tool for viewing the status and configuration of the server and MySQL instances. It uses tools from Percona Toolkit to generate the report. For more information, see sysinfo. user Owner of the PCT Account. 36 Chapter 11. Glossary

41 Index A API key, 35 M Metrics Monitor, 35 O organization, 35 P PCT Account, 35 Percona Agent, 35 Percona Toolkit, 35 Performance Schema, 35 Q Query Analytics, 35 S slow query log, 35 System Info, 36 U user, 36 37