Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 37.9Mb
PDF (A4) - 37.9Mb
PDF (RPM) - 37.3Mb
HTML Download (TGZ) - 10.3Mb
HTML Download (Zip) - 10.3Mb
HTML Download (RPM) - 8.9Mb
Man Pages (TGZ) - 216.7Kb
Man Pages (Zip) - 329.5Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
Excerpts from this Manual

25.4.4 Pre-Filtering by Instrument

The setup_instruments table lists the available instruments:

mysql> SELECT * FROM setup_instruments;
| NAME                                                       | ENABLED | TIMED |
| wait/synch/mutex/sql/LOCK_global_read_lock                 | YES     | YES   |
| wait/synch/mutex/sql/LOCK_global_system_variables          | YES     | YES   |
| wait/synch/mutex/sql/LOCK_lock_db                          | YES     | YES   |
| wait/synch/mutex/sql/LOCK_manager                          | YES     | YES   |
| wait/synch/rwlock/sql/LOCK_grant                           | YES     | YES   |
| wait/synch/rwlock/sql/LOGGER::LOCK_logger                  | YES     | YES   |
| wait/synch/rwlock/sql/LOCK_sys_init_connect                | YES     | YES   |
| wait/synch/rwlock/sql/LOCK_sys_init_slave                  | YES     | YES   |
| wait/io/file/sql/binlog                                    | YES     | YES   |
| wait/io/file/sql/binlog_index                              | YES     | YES   |
| wait/io/file/sql/casetest                                  | YES     | YES   |
| wait/io/file/sql/dbopt                                     | YES     | YES   |

To control whether an instrument is enabled, set its ENABLED column to YES or NO. To configure whether to collect timing information for an enabled instrument, set its TIMED value to YES or NO. Setting the TIMED column affects Performance Schema table contents as described in Section 25.4.1, “Performance Schema Event Timing”.

Modifications to most setup_instruments rows affect monitoring immediately. For some instruments, modifications are effective only at server startup; changing them at runtime has no effect. This affects primarily mutexes, conditions, and rwlocks in the server, although there may be other instruments for which this is true.

The setup_instruments table provides the most basic form of control over event production. To further refine event production based on the type of object or thread being monitored, other tables may be used as described in Section 25.4.3, “Event Pre-Filtering”.

The following examples demonstrate possible operations on the setup_instruments table. These changes, like other pre-filtering operations, affect all users. Some of these queries use the LIKE operator and a pattern match instrument names. For additional information about specifying patterns to select instruments, see Section 25.4.9, “Naming Instruments or Consumers for Filtering Operations”.

  • Disable all instruments:

    mysql> UPDATE setup_instruments SET ENABLED = 'NO';

    Now no events will be collected.

  • Disable all file instruments, adding them to the current set of disabled instruments:

    mysql> UPDATE setup_instruments SET ENABLED = 'NO'
           WHERE NAME LIKE 'wait/io/file/%';
  • Disable only file instruments, enable all other instruments:

    mysql> UPDATE setup_instruments
           SET ENABLED = IF(NAME LIKE 'wait/io/file/%', 'NO', 'YES');
  • Enable all but those instruments in the mysys library:

    mysql> UPDATE setup_instruments
  • Disable a specific instrument:

    mysql> UPDATE setup_instruments SET ENABLED = 'NO'
           WHERE NAME = 'wait/synch/mutex/mysys/TMPDIR_mutex';
  • To toggle the state of an instrument, flip its ENABLED value:

    mysql> UPDATE setup_instruments
           SET ENABLED = IF(ENABLED = 'YES', 'NO', 'YES')
           WHERE NAME = 'wait/synch/mutex/mysys/TMPDIR_mutex';
  • Disable timing for all events:

    mysql> UPDATE setup_instruments SET TIMED = 'NO';

User Comments
Sign Up Login You must be logged in to post a comment.