This topic describes how to use OceanBase Diagnostic Tool (obdiag) that is independently deployed to display the information about slow SQL statements in a cluster in a terminal.
Syntax
obdiag display scene run --scene=observer.slowsql [options]
The following table describes the options.
Option |
Required |
Data type |
Default value |
Description |
|---|---|---|---|---|
| -c | No | string | ~/.obdiag/config.yml |
The path of the configuration file. |
| --inner_config | No | string | Empty | The configurations of obdiag. |
| --config | No | string | Empty | The configurations of the cluster diagnosed by obdiag, in the format of --config key1=value1 --config key2=value2.
NoteFor information about the parameters supported by this option, see Configure obdiag. |
| --env | Yes | string | Empty | Additional parameters required for the obdiag display command, in the format of --env tenant_name=test --env mtime=10. |
Note
In the --env option, mtime indicates the recent period for which slow SQL statements are to be queried, in minutes.
Examples
Method 1: Use the command out-of-the-box without a configuration file
# The --env options are passed to specify the connection string of the target tenant for the query and to specify querying slow SQL statements within the last 10 minutes.
$ obdiag display scene run --scene=observer.slowsql --env tenant_name=test --env mtime=10 \
--config db_host=xx.xx.xx.xx \
--config db_port=xxxx \
--config tenant_sys.user=root@sys \
--config tenant_sys.password=***
Method 2: Use the command with a configuration file
Before you use this command, make sure that you have configured the login information of the target nodes in the config.yml configuration file of obdiag. For more information, see Configure obdiag.
# The --env option is passed to specify the connection string of the target tenant for the query.
obdiag display scene run --scene=observer.slowsql --env tenant_name=test --env mtime=10