Skip to main content

BlueMind SSH

Overview​

BlueMind is a complete unified enterprise messaging and communications solution.

Monitoring Connector Assets​

Monitored Objects​

  • Core: Main BlueMind engine
  • Eas: Mobile connection service
  • Hps: Authentication service
  • Ips: IMAP operations tracking
  • Lmtpd: Email delivery service
  • Milter: Analysis and modification of emails at SMTP Level
  • Webserver: Web application server
  • Xmpp: Instant messaging service

Monitored Metrics​

You can get an overview of all the metrics gathered from BlueMind in the official documentation: https://forge.bluemind.net/confluence/display/BM35/Reference+des+metriques

Metric nameDescription
core.calls.received.success.countSuccessful calls to the core. Unit: Count
core.calls.received.failure.countFailure calls to the core. Unit: Count
core.heartbeat.broadcast.running.countBroadcast routine running. Unit: Count
core.directory.cluster.events.countDirectory Cluster events. Unit: Count
core.request.handling.total.millisecondsTotal time Core spent to handle requests. Unit: ms
core.request.handling.mean.millisecondsMean time Core spent to handle requests. Unit: ms

Prerequisistes​

BlueMind Configuration​

A monitoring account allowed to access unix sockets within /var/run/bm-metrics/ directory must be created on the BlueMind system and be part of the telegraph group.

You can check that the proper monitoring account permissions are set by logging on the BlueMind system using this newly created user and executing this test command:

user$ curl --unix-socket /var/run/bm-metrics/metrics-bm-core.sock http://127.0.0.1/metrics

The command should return some results such as below:

bm-core.callsByRPC,rpc=GET-/api/todolist/{containerUid}/{uid}/_itemchangelog,status=success,meterType=Counter count=1
bm-core.callsByRPC,rpc=GET-/api/externaluser/{domainUid}/{uid}/groups,status=success,meterType=Counter count=2
bm-core.heartbeat.broadcast,state=core.state.stopping,meterType=Counter count=2
...

Setup​

  1. Install the Centreon package on every poller expected to monitor BlueMind servers:
yum install centreon-plugin-Applications-Bluemind-Ssh
  1. Install the monitoring templates from the Centreon Monitoring Connector on the Configuration > Monitoring Connector Manager page

Configuration​

Adding a new host into Centreon, apply the relevant host template matching your instance/cluster type. All of the host templates begin with App-Bluemind-SSH. Once the template set, you have to set values according to the chosen SSH backend.

3 SSH backends are available to connect to the BlueMind server: sshcli, plink and libssh which are detailed below.

sshcli backend​

MandatoryNameDescription
XSSHBACKENDName of the backend: sshcli
SSHUSERNAMEBy 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).

MandatoryNameDescription
XSSHBACKENDName of the backend: plink
SSHUSERNAMEBy default, it uses the user running process centengine on your poller
SSHPASSWORDCan be used. If not set, SSH key authentication is used
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).

libssh backend​

MandatoryNameDescription
XSSHBACKENDName of the backend: libssh
SSHUSERNAMEBy default, it uses the user running process centengine on your poller
SSHPASSWORDCan be used. If not set, SSH key authentication is used
SSHPORTBy default: 22
SSHEXTRAOPTIONSCustomize it with your own if needed. E.g.: --ssh-priv-key=/user/.ssh/id_rsa

With that backend, you don't have to validate the target server fingerprint manually. Nice ;)

FAQ​

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.