New Database Monitoring is a significantly improved
Databases experience for PostgreSQL and MySQL that delivers deeper insights and faster troubleshooting powered by Smartscape.
Until you activate, new capabilities such as Tables, Indexes, and Database schema appear with an Activate New Database Monitoring to get this feature prompt.
New Database Monitoring delivers a significantly improved experience for both PostgreSQL and MySQL users.
For example, you can visualize execution plans and explore your database schema directly in
Databases:


To upgrade, you need to:
You need the permission (settings:objects:write WHERE settings:schemaId = 'builtin:licensing.new-database-monitoring-experience').
You can request your environment administrator to create a custom policy that grants this permission, or use one of the default built-in policies that include the broader settings:objects:write permission: Admin user or Settings Writer.
Make sure at least one Environment ActiveGate version 1.341.0+, with the Extension Execution Controller enabled, can reach your database hosts.
To use New Database Monitoring across all your environments, repeat the upgrade in each environment.
Make sure New Database Monitoring is included in your Dynatrace Platform Subscription (DPS). If it isn't, contact your account team to add it. When you activate it, Dynatrace updates your settings and billing automatically, and your existing data stays unaffected.
You can activate it from
Databases or from
Settings.
Databases To activate New Database Monitoring from within
Databases:
Open
Databases.
In the Overview or Explorer tab, find the New Database Monitoring is now available banner and select How to activate?.

In the New Database Monitoring dialog, under How to get it, select Activate now.

In the Activate new Database Monitoring? dialog, select Activate. New Database Monitoring is enabled immediately, new billing applies moving forward, and your existing data stays unaffected.

To activate New Database Monitoring from within
Settings:

After activating, the New Database Monitoring is now available banner no longer appears and Enable Database Monitoring shows On in
Settings.
You need to update your PostgreSQL and MySQL extensions, and re-run the setup and validation script for each monitored instance. The latest extension requires a different set of database permissions than the previous version.
If you skip this step, some metrics, top queries, or execution plans can stop working.
For each monitored instance:
Update the PostgreSQL and MySQL extensions to at least the following versions:
For detailed steps, see Update an extension from Dynatrace Hub.
Running the onboarding flow again triggers the current installation and validation scripts, which create the dynatrace monitoring user with the required grants, the execution-plan helper function, and the performance_schema (MySQL) or pg_stat_statements (PostgreSQL) settings that the new extension expects.
Re-run the setup and run the validation script to confirm the required permissions and objects are in place.
After re-running onboarding, the Monitor extension status view shows Up to date under Version check for the updated extension.
To confirm that the upgrade is complete, you can repeat these verification steps:
Databases, verify that the New Database Monitoring is now available banner no longer appears.
Databases > Recommendations > Monitor extension status, confirm that each extension shows Up to date under Version check and No errors under Extension logs. The table also lists the installed, required, and minimum configuration versions for each extension.
Databases > Explorer tab, confirm that the Databases, Tables, and Indexes views report current data.
The
Databases > Recommendations tab helps you find and fix common issues after the upgrade—extensions that still need updating, monitoring gaps caused by incomplete onboarding, and databases that aren't monitored yet.
Use Recommendations > Check for monitoring gaps to find instances where monitoring is only partially working. Gaps such as Execution plan not available or Queries not available usually mean onboarding didn't finish, or the dynatrace monitoring user lacks the permissions or helper functions that the latest extension requires.
To resolve a gap:
For the full re-onboarding procedure, see Monitor MySQL database or Monitor PostgreSQL database.

Use Recommendations > Monitor auto-detected Databases to review database instances that Dynatrace discovered in your infrastructure but that aren't monitored yet. For each instance, select Configure monitoring to onboard it.

If Monitor extension status shows Incompatible under Version check, or reports errors under Extension logs, update the affected extension and re-run onboarding. See Upgrade your monitoring configurations.
If you have questions or encounter issues during the upgrade, contact Dynatrace Support.
Databases