Oracle GoldenGate SSH
Monitoring Connector Assets​
Monitored Objects​
The Monitoring Connector includes monitoring of status and lags of Oracle GG Processes thanks to GGSCI command-line utility.
Collected Metrics​
- Processes
Metric name | Description | Unit |
---|---|---|
process status | Process status | |
processname#process.lag.seconds | processus lag at checkpoint | |
processname#process.time.checkpoint.seconds | processus time since checkpoint |
Prerequisites​
The centreon-engine user performs a SSH connection to a remote system user. This user must have enough privileges to run ggsci
command.
Setup​
- Online License
- Offline License
- Install the Centreon Plugin on every Poller:
yum install centreon-plugin-Applications-Oracle-Goldengate-Ssh
- On the Centreon Web interface in Configuration > Monitoring Connector Manager, install the Oracle GoldenGate SSH Monitoring Connector
- Install the Centreon Plugin on every Poller:
yum install centreon-plugin-Applications-Oracle-Goldengate-Ssh
- On the Centreon Central server, install the Centreon Monitoring Connector from the RPM:
yum install centreon-pack-applications-oracle-goldengate-ssh
- On the Centreon Web interface in Configuration > Monitoring Connector Manager, install the Oracle GoldenGate SSH Monitoring Connector
Configuration​
- Add a new Host and apply the App-Oracle-Goldengate-SSH-custom Host Template
Once the template applied, some Macros have to be configured:
Mandatory | Name | Description |
---|---|---|
GGSHOME | Directory of ggsci | |
ORACLEHOME | Oracle home directory |
3 SSH backends are available to connect to the remote server: sshcli, plink and libssh which are detailed below.
- sshcli backend
- plink backend
- libssh backend (default)
Mandatory | Name | Description |
---|---|---|
X | SSHBACKEND | Name of the backend: sshcli |
X | SSHUSERNAME | By default, it uses the user running process centengine on your Poller |
SSHPASSWORD | Cannot be used with backend. Only ssh key authentication | |
SSHPORT | By default: 22 | |
SSHEXTRAOPTIONS | Customize it with your own if needed. E.g.: --ssh-priv-key=/user/.ssh/id_rsa |
With that backend, you have to validate the target server fingerprint manually (with the SSHUSERNAME used).
Mandatory | Name | Description |
---|---|---|
X | SSHBACKEND | Name of the backend: plink |
X | SSHUSERNAME | By default, it uses the user running process centengine on your Poller |
SSHPASSWORD | Can be used. If not set, SSH key authentication is used | |
SSHPORT | By default: 22 | |
SSHEXTRAOPTIONS | Customize it with your own if needed. E.g.: --ssh-priv-key=/user/.ssh/id_rsa |
With that backend, you have to validate the target server fingerprint manually (with the SSHUSERNAME used).
Mandatory | Name | Description |
---|---|---|
X | SSHBACKEND | Name of the backend: libssh |
X | SSHUSERNAME | By default, it uses the user running process centengine on your Poller |
SSHPASSWORD | Can be used. If not set, SSH key authentication is used | |
SSHPORT | By default: 22 | |
SSHEXTRAOPTIONS | Customize it with your own if needed. E.g.: --ssh-priv-key=/user/.ssh/id_rsa |
With that backend, you do not have to validate the target server fingerprint manually.
FAQ​
How to check in the CLI that the configuration is OK and what are the main options for ?​
Once the Plugin installed, log into your Poller using the centreon-engine user account and test by running the following command :
/usr/lib/centreon/plugins/centreon_oracle_gg_ssh.pl \
--plugin=apps::oracle::gg::local::plugin \
--mode=processes \
--hostname=10.30.2.81 \
--ssh-username=centreon \
--ssh-password='centreon-password' \
--ssh-backend=libssh \
--filter-type=REPLICAT \
--verbose
Which output something similar to:
CRITICAL: Process 'REPLICAT:RP_TS02' status: ABENDED | 'REPLICAT:RP_TSO1#process.lag.seconds'=0s;;;0; 'REPLICAT:RP_TSO1#process.time.checkpoint.seconds'=4s;;;0; 'REPLICAT:RP_TS02#process.lag.seconds'=172472s;;;0; 'REPLICAT:RP_TS02#process.time.checkpoint.seconds'=1462s;;;0; 'REPLICAT:RP_TS03#process.lag.seconds'=0s;;;0; 'REPLICAT:RP_TS03#process.time.checkpoint.seconds'=4s;;;0;
Process 'REPLICAT:RP_TSO1' status: RUNNING, lag: 0, time since checkpoint: 4s
Process 'REPLICAT:RP_TS02' status: ABENDED, lag: 1d 23h 54m 32s, time since checkpoint: 24m 22s
Process 'REPLICAT:RP_TS03' status: RUNNING, lag: 0, time since checkpoint: 4s
The command above gets the status of Oracle GoldenGate processes (--mode=processes
).
It uses a SSH username centreon (--ssh-username=centreon
), a SSH password centreon-password (--ssh-password='centreon-password'
),
uses a SSH backend libssh (--ssh-backend='libssh'
) and it connects to the host 10.30.2.81 (--hostname=10.30.2.81
)
on the SSH default port 22 (--ssh-port=22
).
All the options that can be used with this plugin can be found over the --help
options:
/usr/lib/centreon/plugins/centreon_oracle_gg_ssh.pl \
--plugin=apps::oracle::gg::local::plugin \
--mode=processes \
--help
I have that error message: UNKNOWN: Command error: Host key verification failed.
. What does it mean ?​
It means you haven't manually validated the target server fingerprint with ssh
or plink
on the Centreon Poller.