`
zhang_ly520
  • 浏览: 162018 次
  • 性别: Icon_minigender_1
  • 来自: 北京
社区版块
存档分类
最新评论

Monitoring MySQL

阅读更多

Overall activity

Questions

累计值:The number of queries and protocol commands that have been run.

Uptime

当前值:The number of seconds the server has been online.

Uptime_since_flush_status

当前值:The number of seconds since either the server was started or FLUSH STATUS has been run.

 

Connections

Aborted_clients

累计值:A count of the number of clients that did not call mysql_close() or equivalent in their API, and thus the MySQL server forcibly closed their connection.

Aborted_connects

累计值:A count of the number of clients that did not successfully connect due to handshake or network errors in the connect process.

Connections

累计值:The number of clients currently connected.

Max_used_connections

当前值:The maximum number of clients that have been connected since the server started. If this is equal to max_connections configuration variable, you have reached maxed out the connections to the server.

 

Network traffic

Bytes_*

累计值:The number of bytes sent to (Bytes_sent) clients (primarily result sets) and received from (Bytes_received) clients (primarily query text).

 

DML commands

Com_*

累计值:The number of commands of various types that have been run:

  • Com_selectSELECT
  • Com_insertINSERT
  • Com_insert_selectINSERT ... SELECT ...
  • Com_updateUPDATE
  • Com_deleteDELETE

     

    Transactions

    Com_*

    累计值:The number of various transactional commands that have been run:

    • Com_beginBEGIN or START TRANSACTION
    • Com_commitCOMMIT
    • Com_rollbackROLLBACK

     

    Temporary tables

    Created_tmp_tables

    累计值:The number of temporary tables that have been created.

    Created_tmp_disk_tables

    累计值:

    The number of temporary tables that have been converted from in-memory (HEAP) to on-disk (MyISAM) temporary tables. This can occur for one of a few reasons:

    • The table reached tmp_table_size or max_heap_table_size and could no longer be stored in-memory.
    • The table contains BLOB or TEXT column types and couldn’t be created as an in-memory table at all.

     

    Table cache usage

    Opened_tables

    累计值:

    The number of tables that have been opened because there wasn’t an available cached open table in the table cache. This normally implies that either:

    • The FLUSH TABLES command is being run often.
    • The size of table_cache is too small, and tables must be closed in order to open others.

     

    Open_tables

    当前值:The number of tables currently open. If this is equal to the table_cache variable, it would imply that the table_cache setting is too low.

     

    Threads

    Threads_created

    累计值:The number of threads that have been created. This should be stable as long as the thread_cache variable is large enough.

    Threads_cached

    当前值:The number of threads currently in the cache and available for use.

    Threads_connected

    当前值: The number of threads currently handling a connection.

    Threads_running

    当前值: The number of threads currently in a non-idle (Sleep) state.

     

    InnoDB

    InnoDB buffer pool

    Innodb_buffer_pool_pages_*

    当前值: The number of pages in various states in the buffer pool:

    • Innodb_buffer_pool_pages_data — Data pages; containing data or indexes from tables.
    • Innodb_buffer_pool_pages_dirty — Pages marked as "dirty"; having changes that have yet to be written to disk.
    • Innodb_buffer_pool_pages_free — Free pages; available for data to be stored.
    • Innodb_buffer_pool_pages_total — All pages; the total number of pages which can be allocated for InnoDB’s buffer pool. This number will be equal to innodb_buffer_pool_size / Innodb_page_size

     

    Innodb_buffer_pool_*

    累计值:

    • Innodb_buffer_pool_read_requests — The number of requests for a page from the buffer pool. This counter is incremented whether the page exists in the buffer pool, or requires a disk read to fetch the page into the buffer pool.
    • Innodb_buffer_pool_reads — The number of pages that had to actually be read from disk into the buffer pool.
    • Innodb_buffer_pool_write_requests — The number of pages that have been requested to be written from the buffer pool to disk.

     

    Innodb_buffer_pool_read_ahead_*

    累计值:

  • Innodb_buffer_pool_read_ahead_rnd
  • Innodb_buffer_pool_read_ahead_seq

     

    Buffer pool miss rate

    100 * (Innodb_buffer_pool_reads / Innodb_buffer_pool_read_requests)

     

    The buffer pool miss rate is the percentage of the time that a page was requested but was not present in the buffer pool and had to be read from the disk. Increasing the size of innodb_buffer_pool_size may decrease the number of buffer pool misses.

    The inverse of this (100 – miss rate) is the buffer pool hit rate.

     

    Percent of dirty pages

    100 * (Innodb_buffer_pool_pages_dirty/Innodb_buffer_pool_pages_data)

     

    The percent of dirty pages is a ratio of many pages are in the cache in a modified state (dirty) and shoudl be written to disk before shutdown.

     

    Percent buffer pool used for data

    100 * (Innodb_buffer_pool_pages_data/Innodb_buffer_pool_pages_total)

     

    The percent of the buffer pool used for data is a ratio of how many pages are currently allocated for data and index pages in the buffer pool.

     

    Percent buffer pool free

    100 * (Innodb_buffer_pool_pages_free/Innodb_buffer_pool_pages_total)

     

    The percent of the buffer pool free is the ratio of how many pages are not currently allocated in the buffer pool. These pages may or may not have been allocated from the operating system by MySQL/InnoDB. That is they may really be "free" as in entirely unallocated, or they may be "free in the buffer pool", allocated but currently unused.

     

    InnoDB_data_*

    累计值:

    • Innodb_data_reads — The number of times data has been read.
    • Innodb_data_read — The amount of data read (in bytes) because of Innodb_data_reads.
    • Innodb_data_writes — The number of times data has been written.
    • Innodb_data_written — The amount of data written (in bytes) because of Innodb_data_writes.

     

    InnoDB_pages_*

    累计值:

    • Innodb_pages_created — The number of pages that were newly created because of new data being inserted or updated and pages being appended or split.
    • Innodb_pages_read — The number of pages that have been read because they were not present in the buffer pool.
    • Innodb_pages_written — The number of pages that have been written or rewritten.

     

    InnoDB_rows_*

    累计值:

    • Innodb_rows_deleted — The number of rows that have been deleted.
    • Innodb_rows_inserted — The number of rows that have been inserted.
    • Innodb_rows_read — The number of rows that have been read.
    • Innodb_rows_updated — The number of rows that have been updated.

     

    MyISAM

    Key buffer size

    • Key_blocks_used
    • Key_blocks_unused
    • Key_blocks_not_flushed

    Key buffer activity

    Key_*
    • Key_reads
    • Key_writes

    Key_*_requests
    • Key_read_requests
    • Key_write_requests

    Key buffer misses
    100 * (Key_reads / Key_read_requests)

     

    Key buffer write coalesces
    (Key_write_requests / Key_writes)

     

  • 分享到:
    评论

    相关推荐

      mysql 监控 Monitoring_MySQL mysql_en mysql

      ### MySQL监控:基础知识与实例 #### 一、MySQL简介及特性 MySQL作为一款知名的开源数据库管理系统,由MySQL AB公司开发并维护,后被Sun Microsystems收购。MySQL的特点包括但不限于以下几点: - **开源性**:...

      MySQL 8 Cookbook epub 格式

      The book also contains recipes on efficient MySQL administration, with tips on effective user management, data recovery, security, database monitoring, performance tuning, troubleshooting, and more. ...

      docker安装skywalking+mysql

      SkyWalking是一个应用于微服务架构的可观测性平台,它提供了APM(Application Performance Monitoring)功能,包括分布式追踪、服务网格指标收集等。要安装SkyWalking-OAP服务器,运行一个Docker容器,暴露所需的...

      MySQL V5.5帮助文档

      1.5.4. Diagnostic and Monitoring Capabilities 1.6. MySQL Information Sources 1.6.1. MySQL Mailing Lists 1.6.2. MySQL Community Support at the MySQL Forums 1.6.3. MySQL Community Support on Internet ...

      MySQL数据库巡检手册

      4. **性能监控**:阐述如何通过命令行工具(如`SHOW STATUS`、`SHOW VARIABLES`)和图形界面工具(如MySQL Workbench、Percona Monitoring and Management)进行性能监控,识别潜在性能瓶颈。 5. **查询优化**:...

      高性能Mysql mysql书籍

      5. **性能监控与调优工具**:介绍了一些用于监控MySQL性能的工具,如MySQL Enterprise Monitor、Percona Monitoring Plugins,以及如何利用这些工具进行性能分析和调优。 6. **内存管理与缓存**:探讨了MySQL如何...

      MySQL大佬姜承尧49完整课程笔记,进阶涨薪必看,内含MySQL配置文件

      - 监控工具:使用如MySQL Enterprise Monitor、Percona Monitoring and Management等工具进行性能监控。 - 查询分析器:使用EXPLAIN分析SQL执行计划,找出性能瓶颈。 - 参数调整:根据系统负载调整MySQL的配置...

      Enterprise-Ready Database, Monitoring and Support with MySQL Enterprise

      在探讨《企业级数据库、监控与支持:MySQL Enterprise》这一主题时,我们深入解析了如何通过MySQL Enterprise解决方案来最大化安全、性能与可用性,尤其是在构建和维护数据驱动的在线应用时,面对开源Web 2.0技术所...

      MYSQL高效编程_MYSQL_

      - **性能监控**:介绍如何使用工具(如MySQL Enterprise Monitor、Percona Monitoring Plugins)监控数据库性能。 - **错误日志分析**:讲解如何通过分析错误日志排查问题和优化数据库运行。 8. **最新版本特性**...

      mysql数据在linux环境下各种安装

      监控工具如MySQL Enterprise Monitor或Percona Monitoring Plugins可以帮助了解数据库的运行状态,及时发现和解决问题。 在提供的压缩包"mysql安装文档(linux)"中,你将找到更详细的步骤和配置示例,帮助你根据实际...

      Spotlight_on_mysql

      - **第三方工具**:例如Percona Monitoring and Management (PMM)、MySQL Enterprise Monitor等,提供更全面的监控和分析功能,包括历史数据对比和警报设置。 - **日志分析**:通过分析MySQL日志,可以找出性能...

      mysql全套安装包----rpm

      同时,可以安装监控工具如MySQL Enterprise Monitor或Percona Monitoring Plugins来监控MySQL的运行状态。 通过以上步骤,你就能在CentOS 6/6.5系统上成功安装和配置MySQL数据库。确保定期更新和维护MySQL,以保持...

      数据库mysql5.6安装部署

      - **监控**: 利用MySQL自带的性能监控工具或第三方工具如Percona Monitoring and Management (PMM)进行性能监控。 - **性能调优**: 通过调整配置文件中的参数来优化MySQL性能。 #### 六、总结 通过上述步骤,我们...

      mysql DBA学习笔记

      了解如何通过监控工具(如Mysql Enterprise Monitor、Percona Monitoring Plugins)收集MySQL性能指标,设置阈值报警,以便及时发现并解决问题。 九、安全性 数据库的安全管理包括用户权限控制、加密技术、审计日志...

      alpine-mysql:Docker镜像MySQL(Alpine)

      MYSQL_USER_MONITORING : monitoring , MYSQL_PASSWORD_MONITORING : monitoring 自定义:在.env文件中,更改不同的值以适合您的需求。 指令 拉: docker pull quay.io/perriea/alpine-mysql:1.0 运行: ...

      mysql 性能优化与架构设计(word版)

      1. MySQL性能监控:如pt-query-digest、Percona Monitoring and Management (PMM) 可以分析慢查询日志,找出性能瓶颈。 2. 系统资源监控:使用工具如top、iostat、vmstat、sysstat等监控CPU、内存、磁盘I/O和网络...

      Mysql Mysql学习资料

      - 监控工具:如MySQL Enterprise Monitor、Percona Monitoring and Management等,用于性能监控和问题诊断。 - 性能分析:使用EXPLAIN分析查询性能,调整索引,优化SQL语句。 - 调整配置:根据系统资源和负载调整...

      MySql DBA Tutorials PPT

      - MySQL监控工具,如MySQL Enterprise Monitor、Percona Monitoring Plugins。 - 使用性能分析工具如pt-query-digest分析慢查询。 - 资源使用监控,如CPU、内存和磁盘I/O。 11. **云环境下的MySQL** - 在AWS ...

    Global site tag (gtag.js) - Google Analytics