Bug #78311 Transaction consumers enabled but not the instrument

• Submitted: 3 Sep 2015 3:11
• Modified: 1 Oct 2015 17:35
• Reporter: Jesper wisborg Krogh
• Status: Closed
• Category: MySQL Server: Performance Schema
• Severity: S3 (Non-critical)
• Version: 5.7.8
• OS: Any
• CPU Architecture: Any

[3 Sep 2015 3:11] Jesper wisborg Krogh

Description:
By default the current and history consumer events for transactions are enabled, but the instrument is disabled. This causes confusion as it makes it appear like transaction instrumentation is enabled by default, but in fact isn't. 

How to repeat:
mysql> SELECT * FROM performance_schema.setup_consumers WHERE NAME LIKE '%transactions%';
+----------------------------------+---------+
| NAME                             | ENABLED |
+----------------------------------+---------+
| events_transactions_current      | YES     |
| events_transactions_history      | YES     |
| events_transactions_history_long | NO      |
+----------------------------------+---------+
3 rows in set (0.04 sec)

mysql> SELECT * FROM performance_schema.setup_instruments WHERE NAME = 'transaction';
+-------------+---------+-------+
| NAME        | ENABLED | TIMED |
+-------------+---------+-------+
| transaction | NO      | NO    |
+-------------+---------+-------+
1 row in set (0.00 sec)

Suggested fix:
Either enable the transaction instrument of disable events_transactions_% so consumers and instruments are aligned.

[1 Oct 2015 17:35] Paul DuBois

Noted in 5.7.9, 5.8.0 changelogs.

Previously, the transaction instrument in the setup_instruments table
was disabled by default, and the events_transactions_current and
events_transactions_history consumers in the setup_consumers table
were enabled by default. This setup is inconsistent, and having the
consumers enabled could lead to the impression that transactions were 
instrumented by default. Now, the consumers are also disabled by
default. To monitor transactions, enable the instrument and the
applicable consumers.