Database Autonomy Service:Session management

Real-time metrics

The section header displays the following metrics:

Run 10-second SQL analysis

Click 10s SQL Analysis in the upper-right corner of the section. The dialog box displays query activity captured over a 10-second window, including:

• Summary information

• Slow query logs

• SQL overview

For more information, see 10-second SQL analysis.

Enable SQL throttling

Click SQL Throttling to open the SQL Throttling dialog box. Configure the parameters to apply threshold-based SQL throttling on sessions.

For more information, see SQL throttling.

Optimize SQL

Click Optimize in the session list to optimize a SQL statement.

For more information, see SQL optimization.

Export active sessions

Export active sessions from the Instance Sessions section.

Terminate sessions

To terminate a session, enter the account and password of the database in which the session was created. You can also use an account that has the permissions to terminate sessions created by other accounts, such as a privileged account.

• The User column shows the database account that created each session.

• Click End Session History to view records of terminated sessions.

Why does a percent sign (%) appear in the Access Source column?

A percent sign (%) may appear in the Access Source column on the Source Statistics tab of the SQL Explorer tab when a stored procedure is used.

The following steps reproduce this behavior. In this example, the database instance is an ApsaraDB RDS for MySQL instance, the test account is test_user, and the test database is testdb.

1. Create a database and a standard account, and grant permissions on the database to the standard account in the ApsaraDB RDS console. For details, see Create accounts and databases.

2. Connect to the instance as test_user by using the CLI. For details, see Use a database client or the CLI to connect to an ApsaraDB RDS for MySQL instance.

3. Switch to the testdb database and create a stored procedure:

   -- Switch to the testdb database.
   USE testdb;
   
   -- Create a stored procedure.
   DELIMITER $$
   DROP PROCEDURE IF EXISTS `das` $$
   CREATE DEFINER=`test_user`@`%` PROCEDURE `das`()
   BEGIN
   SELECT * FROM information_schema.processlist WHERE Id = CONNECTION_ID();
   END $$
   DELIMITER;

4. Connect to the database instance with a privileged account. For details, see Use a database client or the CLI to connect to an ApsaraDB RDS for MySQL instance.

5. Call the stored procedure:

   -- Switch to the testdb database.
   USE testdb;
   
   -- Call the stored procedure.
   CALL das();
   
   +--------+-----------+--------+--------+---------+------+-----------+-------------------------------------------------------------------------+
   | ID     | USER      | HOST   | DB     | COMMAND | TIME | STATE     | INFO                                                                    |
   +--------+-----------+--------+--------+---------+------+-----------+-------------------------------------------------------------------------+
   | 487818 | test_user | %:2065 | testdb | Query   |    0 | executing | SELECT * FROM information_schema.processlist WHERE Id = CONNECTION_ID() |
   +--------+-----------+--------+--------+---------+------+-----------+-------------------------------------------------------------------------+

The HOST column shows %:2065, which causes the percent sign to appear in the Access Source column.

What sessions are marked as abnormal for ApsaraDB RDS for MySQL instances and PolarDB for MySQL clusters?

The following sessions are marked as abnormal: