Parameter inspection and comparison
Use the parameter inspection and comparison feature of Database Autonomy Service (DAS) to check and compare parameter settings across database instances.
Prerequisites
-
The database instance runs one of the following engines:
-
ApsaraDB RDS for MySQL
-
PolarDB for MySQL
-
-
The database instance is connected to DAS and its status is Normal Access. For more information, see Connect a database instance to DAS.
-
For more information about limitations, see Limitations.
Procedure
Create a rule
-
Log in to the DAS console.
-
In the left navigation bar, click Tools > Inspection and Scoring.
-
On the page that opens on the right, click Parameter Inspection and Comparison.
-
Click Settings to go to the rule template page for Parameter Inspection and Comparison, click Rule Management, and then click Create Rule on the page that appears. After you enter the corresponding parameters, click OK to add the new rule.
NoteThis example creates a parameter comparison rule for the MySQL engine to check whether the
innodb_adaptive_hash_indexparameter is set toOFF. -
After the rule is added, you can view existing rules on the Rule Management page.
For example, the
innodb_adaptive_hash_indexrule appears in the list with a type of Parameter Comparison and a parameter value of User-defined Value.
Create a template
-
On the Rule Templates page, click Create Template. Enable the template, associate the rule you created for
innodb_adaptive_hash_index, and select the instances to check. Click OK to create the template.Enter a Template Alias and Template Remarks (for example,
innodb_adaptive_hash_index), and set the Period as needed. -
After the template is added, you can view existing templates on the Rule Templates page.
The page lists information such as the template alias/ID, remarks, associated rule alias/ID, period, and status. In the Actions column, you can click Details, Select Instance, or Delete. For example, the
innodb_adaptive_hash_indextemplate shows an enabled status.
Initiate a task
-
Return to the Parameter Inspection and Comparison page, select the corresponding engine type, and click Initiate Task.
-
In the panel that opens on the right, select a task type.
-
For example, to use the MySQL parameter comparison template you created, click the Parameter Comparison tab, click Select Template, select the template, and then click Initiate Task.
-
You can also select instances directly for an ad hoc comparison of their parameter settings.
In the Parameter Inspection and Comparison dialog box, click the Parameter Comparison > Select Instance tab. Move the target instances from the list of available instances on the left to the list of selected instances on the right, and then click Initiate Task.
-
View the report
-
On the Parameter Inspection and Comparison page, view historical analysis tasks. Click View Report in the Actions column to view the analysis report details.
-
For example, a MySQL parameter comparison report contains three sections:
-
Basic Information: Basic information about the task.
-
Task Template Details: Rule and template configuration details.
-
Instance Parameter Comparison: Runtime values of instance parameters and the comparison values (if set).
The report contains three sections: Basic information (task type, engine, start time, end time, and initiation type), Task template details (template ID, alias, period, status, associated instances, and rules), and the Instance parameter comparison table. The table provides a multi-column comparison of parameter runtime values across instances, showing how parameters such as
innodb_adaptive_hash_indexdiffer between instances of various versions and specifications.Click Select Instance to filter the view and see parameter differences for specific instances.
The search box in the upper-right corner supports filtering by parameter name. The Value column displays the parameter values defined in your configuration rules, if any.
For example, if you enter
innodb_adaptive_hash_indexin the search box, you can view the differences for this parameter across instances. The runtime value is ON for a MySQL 8.0 instance and OFF for a MySQL 5.7 instance. The comparison value is OFF.
-