# MySQL Extension Requirements Removed

**URL:** <https://community.dynatrace.com/t/mysql-extension-requirements-removed/54132>\
**Category:** Extensions\
**Tags:** databases, mysql\
**Created:** [November 19, 2025, 1:35pm UTC](https://community.dynatrace.com/t/mysql-extension-requirements-removed/54132 "2025-11-19T13:35:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![NicoleMT](https://avatars.discourse-cdn.com/v4/letter/n/3be4f8/32.png) [@NicoleMT](https://community.dynatrace.com/u/NicoleMT)\
**Post date:** [November 19, 2025, 1:35pm UTC](https://community.dynatrace.com/t/mysql-extension-requirements-removed/54132/1 "2025-11-19T13:35:59Z")

</div>

Hello, on November 17 I configured a MySQL extension, and at that time the documentation listed the following requirements:

**Requirements for the MySQL extension**  
MySQL user with native authentication

Create user:

CREATE USER ‘dynatrace’@‘%’ IDENTIFIED WITH mysql\_native\_password BY ‘password’;

Grant permissions:

GRANT SELECT ON performance\_schema.\* TO ‘dynatrace’@‘%’; GRANT PROCESS ON \*.\* TO ‘dynatrace’@‘%’; GRANT SHOW DATABASES ON \*.\* TO ‘dynatrace’@‘%’; GRANT SELECT ON mysql.slow\_log TO ‘dynatrace’@‘%’; GRANT SELECT ON sys.x$memory\_global\_by\_current\_bytes TO ‘dynatrace’@‘%’;

Note: To obtain database sizes, SELECT must be granted on each individual database.

**CPU Metrics**

SET GLOBAL innodb\_monitor\_enable=‘cpu%’;

**Top Slow Queries**  
Enable slow logging to table:

SET GLOBAL log\_output = ‘TABLE’; SET GLOBAL slow\_query\_log = ‘ON’; SET GLOBAL long\_query\_time = 2;

Enable statement instruments and consumers:

UPDATE performance\_schema.setup\_instruments SET ENABLED = ‘YES’, TIMED = ‘YES’ WHERE NAME LIKE ‘statement/%’; UPDATE performance\_schema.setup\_consumers SET ENABLED = ‘YES’ WHERE NAME IN (‘events\_statements\_history’, ‘events\_statements\_summary\_by\_digest’);

**Execution Plan**

Create procedure:

CREATE SCHEMA IF NOT EXISTS dynatrace; DELIMITER $$ CREATE PROCEDURE dynatrace.dynatrace\_execution\_plan(IN query TEXT) SQL SECURITY DEFINER BEGIN SET @explain := CONCAT('EXPLAIN FORMAT=JSON ', query); PREPARE stmt FROM @explain; EXECUTE stmt; DEALLOCATE PREPARE stmt; END $$ DELIMITER ;

Grant permission:

GRANT EXECUTE ON PROCEDURE dynatrace.dynatrace\_execution\_plan TO ‘dynatrace’@‘%’;

Now this information no longer appears in the extension documentation.

I would like to know whether these requirements are still needed and if they have any impact on the database. We also want to see execution plans and slow queries, but this information is still not displayed by the extension.

Any guidance or updates on the current requirements for the extension would be appreciated.

---

<div class="post-metadata">

**Author:** ![JamesKitson](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jameskitson/32/22460_2.png) [@JamesKitson](https://community.dynatrace.com/u/JamesKitson)\
**Post date:** [November 19, 2025, 9:18pm UTC](https://community.dynatrace.com/t/mysql-extension-requirements-removed/54132/2 "2025-11-19T21:18:16Z")

</div>

Recently, all of the ‘documentation’ portions of the Hub tiles was moved to [docs.dynatrace.com](http://docs.dynatrace.com) from the Hub tiles. The Hub tiles still have the releases/release notes but you’ll see the details such as this in the docs now. There is a link to ‘Documentation’ on the Hub tile that will take you to the appropriate page.

For MySQL it is here:&nbsp;[MySQL (remote monitoring) extension — Dynatrace Docs](https://docs.dynatrace.com/docs/observe/applications-and-microservices/databases/extensions/mysql-remote-monitoring-v2)
