This article is applicable to the scenario of independent deployment of obdiag. It can be executed with one click to display the cluster's event information on the terminal.
Instructions for use
obdiag display scene run --scene=observer.event [options]
The options are explained below:
Option name |
Is it required |
Data type |
Default value |
Description |
|---|---|---|---|---|
| -c | No | string | ~/.obdiag/config.yml |
Configuration file path. |
| --inner_config | No | string | Default is empty | obdiag's own configuration. |
| --config | No | string | Default is empty | Configuration of the cluster to be diagnosed by obdiag, fixed style: --config key1=value1 --config key2=value2.
ExplanationParameters that support configuration through this option can be found in obdiag configuration. |
| --env | Yes | string | Default is empty | Additional parameters required for obdiag display, fixed style: --env tenant_name=xxx. |
| --config_password | No | string | Default is empty | obdiag When using an encrypted configuration file, you need to pass in the corresponding password through this option.
ExplanationFor details, please see Configuration file encryption. |
Description
In the optional parameter --env, tenant_name needs to be configured as the business tenant name of the event information to be displayed.
Usage example
Method 1: Use without configuration file (out of the box)
obdiag display scene run --scene=observer.event --env tenant_name=test \
--config db_host=xx.xx.xx.xx \
--config db_port=xxxx \
--config tenant_sys.user=root@sys \
--config tenant_sys.password=***
Method 2: Use with configuration file
You need to ensure that the login information of the node to be collected has been configured in the obdiag configuration file config.yml. For related detailed configuration introduction, see obdiag configuration.
obdiag display scene run --scene=observer.event --env tenant_name=test
Interpretation of results
After the command is executed, the results will be displayed on the current terminal.
# Pass tenant connection string via --env
$ obdiag display scene run --scene=observer.event --env tenant_name=test
display_scenes_run start ...
execute tasks: observer.event
+-----------+-------------+-------------+----------------+
| tenant_id | event_group | total_waits | time_waited |
+-----------+-------------+-------------+----------------+
| 1004 | IO | 1317 | 0.3403 |
| 1004 | LATCH | 9 | 0.0210 |
| 1004 | OTHER | 13133760614 | 192831577.5354 |
| 1004 | SYNC_RPC | 10 | 0.4839 |
+-----------+-------------+-------------+----------------+
Trace ID: a7d52e6c-8a21-11ef-9c0c-00163e01c7ce