## Stage Event Consumers 

These consumers require both global_instrumentation  and thread_instrumentation  to be YES or they are not checked. If checked, they act as follows: 

• events_stages_current , if NO , disables collection of individual stage events in the events_stages_current  table. If YES , it enables stage event collection and the Performance Schema checks the events_stages_history  and events_stages_history_long  consumers. 

• events_stages_history  is not checked if event_stages_current  is NO . Otherwise, an events_stages_history  value of NO  or YES  disables or enables collection of stage events in the events_stages_history  table. 

• events_stages_history_long  is not checked if event_stages_current  is NO . Otherwise, an events_stages_history_long  value of NO  or YES  disables or enables collection of stage events in the events_stages_history_long  table. 

## Statement Event Consumers 

These consumers require both global_instrumentation  and thread_instrumentation  to be YES or they are not checked. If checked, they act as follows: 

• events_statements_current , if NO , disables collection of individual statement events in the events_statements_current  table. If YES , it enables statement event collection and the Performance Schema checks the events_statements_history  and events_statements_history_long  consumers. 

• events_statements_history  is not checked if events_statements_current  is NO . Otherwise, an events_statements_history  value of NO  or YES  disables or enables collection of statement events in the events_statements_history  table. 

• events_statements_history_long  is not checked if events_statements_current  is NO . Otherwise, an events_statements_history_long  value of NO  or YES  disables or enables collection of statement events in the events_statements_history_long  table. 

## Transaction Event Consumers 

These consumers require both global_instrumentation  and thread_instrumentation  to be YES or they are not checked. If checked, they act as follows: 

• events_transactions_current , if NO , disables collection of individual transaction events in the events_transactions_current  table. If YES , it enables transaction event collection and the Performance Schema checks the events_transactions_history  and events_transactions_history_long  consumers. 

• events_transactions_history  is not checked if events_transactions_current  is NO . Otherwise, an events_transactions_history  value of NO  or YES  disables or enables collection of transaction events in the events_transactions_history  table. 

• events_transactions_history_long  is not checked if events_transactions_current  is NO . Otherwise, an events_transactions_history_long  value of NO  or YES  disables or enables collection of transaction events in the events_transactions_history_long  table. 

## Statement Digest Consumer 

The statements_digest  consumer requires global_instrumentation  to be YES  or it is not checked. There is no dependency on the statement event consumers, so you can obtain statistics per 

