Scenarios
You can use the obdiag rca run command to analyze the oms_full_trans scenario.
Supported environment variables
| Variable | Required | Data type | Default value | Description |
|---|---|---|---|---|
| component_id | Yes | string | "" | The ID of the component. You can obtain it in the OceanBase Migration Service (OMS) console by choosing OPS & Monitoring > Component and selecting the component type. The value of Name is the ID of the corresponding component. Generally, a component ID is in the format of {IP address}_connector_xxxxxx. |
Examples
Specify the scenario and component ID in the command.
obdiag rca run --scene=oms_full_trans --env component_id=xxxxxx
Configure cluster information in obdiag
When you use OceanBase Diagnostic Tool (obdiag) for OMS-related diagnostics, namely that the value of --scene starts with oms, you need to configure the OMS cluster information. By default, the config.yml configuration file is stored in the ~/.obdiag directory. You can also use the --config option to pass configuration information. Here is an example:
oms:
oms_name: oms_cluster
servers:
nodes:
- ip: 127.0.0.1
global:
ssh_username: admin # your username
ssh_password: '' # password if need
# ssh_port: 22 # your ssh port, default 22
# ssh_key_file: "" # your ssh-key file path if need
# ssh_type: remote # ssh_type choice [remote, docker, kube] default remote
# container_name: xxx # container_name for ssh_type is docker
# The directory for oms log
log_path: /home/admin/logs
# The directory for oms task's run path
run_path: /home/ds/run
# The directory for oms task's store path
store_path: /home/ds/store