Skip to main content


Pack Assets

Monitored Objects

The Pack IBM Tivoli System Automation for Multiplatforms collects metrics for:

  • Resource-groups

Discovery rules

Rule nameDescription
App-Ibm-Tsamp-SSH-Resource-Group-NameDiscover resource groups and monitor status

Collected Metrics

Metric nameDescriptionUnit
resource_groups.unknown.countNumber of unknown resource groups
resource_groups.offline.countNumber of offline resource groups of online resource groups
resource_groups.failed_offline.countNumber of failed offline resource groups
resource_groups.stuck_online.countNumber of stuck online resource groups
resource_groups.pending_online.countNumber of pending online resource groups
resource_groups.pending_offline.countNumber of pending offline resource groups
resource_groups.ineligible.countNumber of ineligible resource groups
status resource groupCurrent state of the resource group


The centreon-engine user performs a SSH connection to a remote system user. This user must have enough privileges to run lssam command.


  1. Install the Centreon Plugin on every Poller:
yum install centreon-plugin-Applications-Ibm-Tsamp-Ssh
  1. On the Centreon Web interface in Configuration > Monitoring Connector Manager, install the IBM TSAMP SSH Pack

Host configuration

  • Add a new Host and apply the App-Ibm-Tsamp-SSH-custom Host Template

Once the template applied, some Macros have to be configured. 3 SSH backends are available to connect to the remote server: sshcli, plink and libssh which are detailed below.

XSSHBACKENDName of the backend: sshcli
XSSHUSERNAMEBy default, it uses the user running process centengine on your Poller
SSHPASSWORDCannot be used with backend. Only ssh key authentication
SSHPORTBy default: 22
SSHEXTRAOPTIONSCustomize it with your own if needed. E.g.: --ssh-priv-key=/user/.ssh/id_rsa

Warning With that backend, you have to validate the target server fingerprint manually (with the SSHUSERNAME used).

How to test the Plugin 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/ \
--plugin=apps::ibm::tsamp::local::plugin \
--mode=resource-groups \
--hostname= \
--ssh-username=centreon \
--ssh-password='centreon-password' \
--ssh-backend=libssh \

Expected command output is shown below:

OK: All resource groups are ok | 'resource_groups.unknown.count'=0;;;0; 'resource_groups.offline.count'=0;;;0; ''=5;;;0; 'resource_groups.failed_offline.count'=0;;;0; 'resource_groups.stuck_online.count'=0;;;0; 'resource_groups.pending_online.count'=0;;;0; 'resource_groups.pending_offline.count'=0;;;0; 'resource_groups.ineligible.count'=0;;;0;
Resource group 'db2_db2inst1_db2inst1_AUDIT-rg' operational state: online [nominal: online]
Resource group 'db2_db2inst1_db2inst1_AUDIT2-rg' operational state: online [nominal: online]
Resource group 'db2_db2inst1_db2inst1_TCDB-rg' operational state: online [nominal: online]
Resource group 'db2_db2inst1_netdb101-v_0-rg' operational state: online [nominal: online]
Resource group 'db2_db2inst1_netdb102-v_0-rg' operational state: online [nominal: online]

The command above gets resource groups statuses (--mode=resource-groups).

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 (--hostname= on the SSH default port 22 (--ssh-port=22).

All the options as well as all the available thresholds can be displayed by adding the --help parameter to the command:

/usr/lib/centreon/plugins/ \
--plugin=apps::ibm::tsamp::local::plugin \
--mode=resource-groups \


Troubleshooting plugins