Pre-Filtering by Consumer •Destinations associated with a consumer receive no events unless the Performance Schema checks the consumer and the consumer is enabled. •A consumer is checked only if all consumers it depends on (if any) are enabled. •If a consumer is not checked, or is checked but is disabled, other consumers that depend on it are not checked. •Dependent consumers may have their own dependent consumers. •If an event would not be sent to any destination, the Performance Schema does not produce it. The following lists describe the available consumer values. For discussion of several representative consumer configurations and their effect on instrumentation, see Section 27.4.8, “Example Consumer Configurations” . •Global and Thread Consumers •Wait Event Consumers •Stage Event Consumers •Statement Event Consumers •Transaction Event Consumers •Statement Digest Consumer • global_instrumentation  is the highest level consumer. If  global_instrumentation  is  NO , it disables global instrumentation. All other settings are lower level and are not checked; it does not matter what they are set to. No global or per thread information is maintained and no individual events are collected in the current-events or event-history tables. If  global_instrumentation is  YES , the Performance Schema maintains information for global states and also checks the thread_instrumentation  consumer. • thread_instrumentation  is checked only if  global_instrumentation  is  YES . Otherwise, if  thread_instrumentation  is  NO , it disables thread-specific instrumentation and all lower-level settings are ignored. No information is maintained per thread and no individual events are collected in the current-events or event-history tables. If  thread_instrumentation  is  YES , the Performance Schema maintains thread-specific information and also checks  events_ xxx _current  consumers. • events_waits_current , if  NO , disables collection of individual wait events in the events_waits_current  table. If  YES , it enables wait event collection and the Performance Schema checks the  events_waits_history  and  events_waits_history_long  consumers. • events_waits_history  is not checked if  event_waits_current  is  NO . Otherwise, an events_waits_history  value of  NO  or  YES  disables or enables collection of wait events in the events_waits_history  table. • events_waits_history_long  is not checked if  event_waits_current  is  NO . Otherwise, an events_waits_history_long  value of  NO  or  YES  disables or enables collection of wait events in the events_waits_history_long  table. These consumers require both  global_instrumentation  and  thread_instrumentation  to be  YES or they are not checked. If checked, they act as follows: Global and Thread Consumers Wait Event Consumers 4916