Applicable scenarios
This article applies to OMS obcdc component analysis scenarios.
Can import environment variables
Variable name |
Is it required |
Data type |
Default value |
Description |
|---|---|---|---|---|
| component_id | Yes | string | "" | Component ID, which can be obtained by accessing the OMS console -> Operation and Maintenance -> Component -> {Target component type} -> Name. The name is the corresponding component ID. The general composition is {IP information}_xxxxx |
Usage example
The execution example of configuring the analysis scenario and configuring the component ID is as follows:
obdiag rca run --scene=oms_obcdc --env component_id=xxxxxx
obdiag cluster configuration information
When using OMS-related diagnosis (--scene name starts with oms), you need to configure OMS cluster information. The default configuration file address is ~/.obdiag/config.yml. You can also pass the configuration through the --config option. An example of modifying the configuration file is as follows:
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