MySQL And MariaDB Activity

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

MySQL and MariaDB Activity shows current sessions and workload for a monitored MySQL or MariaDB server.

Workflow

Open the MySQL or MariaDB server.
Select Activity.
Review active sessions, query text, waits or state values where available.
Investigate long-running and blocking sessions first.
Open MySQL And MariaDB Execution Plans where plan tree, JSON, diagram, or operators are available.
Continue to Queries, InnoDB, or Deadlocks.

Live And Historical Activity

The MySQL and MariaDB Activity page includes the Mini DBA Time Range selector. Use Live to watch current sessions, blockers, states, and long-running statements, or switch to Last Hour, Last 12 Hours, Last Day, Last Week, or Custom to review captured session history. Mini DBA loads and caches the selected historical activity dataset for the current console session and server context, so reviewing the loaded historical sessions and moving between related views stays quick. Use Back to Live to resume live updates, then choose another historical range when you need a different incident window.

How To Interpret MySQL And MariaDB Activity

Use Activity when a MySQL or MariaDB workload is slow now and you need to see what sessions are doing. The page helps identify long-running statements, blocked sessions, repeated application queries, and connection pressure. It is often the best starting point before moving into historical query or engine-level pages.

Review the longest-running active sessions first, then check whether many sessions share the same state, command, host, database, or application user. A single long query may need query tuning, while many sessions in the same state can indicate a wider resource problem. If lock or transaction symptoms are present, continue to MySQL And MariaDB InnoDB and MySQL And MariaDB Deadlocks.

Activity is also useful for connection troubleshooting. A sudden increase in sleeping connections, repeated connection attempts, or many sessions from one host may point to application pooling behavior rather than a database engine fault.

When a selected session includes execution plan data, use the Diagram, Tree, JSON, and Operators views to identify risky access methods, row estimates, chosen keys, and Extra values. You can also pass the plan to the AI Assistant for focused tuning recommendations.