Skip to content

New release of the Mesos and OpenStack probe
Compare
Choose a tag to compare
@jose-sanchezm jose-sanchezm released this 28 Jun 07:38
· 59 commits to master since this release
1.4-mesos-openstack
1dca510
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

OpenStack probe

  • Updated to version 1.4
  • Updated to provide new convention of groups and hosts (read below)

Mesos probe

  • Updated to version 1.4
  • CMDB integration now is mandatory, so cmdb.location property now is mandatory in the configuration
  • Updated to provide new convention of groups and hosts (read below)

Groups and hosts semantics

This release changes the semantics of groups and hosts when sending metrics to the Zabbix server:

  • Since CMDB integration is now mandatory for both probes, provider name will be used as group name when sending metrics to the server
  • Host name will be the service ID

So for example, if we have two providers with the following services:

  • IFCA
    • "s1": Mesos
    • "s2": OpenStack1
    • "s3": OpenStack2
  • INFN
    • "s1": OpenStack

In this case, this means that the provider IFCA has one Mesos cluster and two OpenStack instances running while the provider INFN has just one OpenStack installation.

In this scenario the OpenStack probe will create two groups (if they don't exist) named IFCA and INFN and it will register metrics under the host name s2 and s3 for group IFCA and s1 for group INFN, meaning that metrics under the host s2 and group IFCA will be the ones related to the OpenStack1 instance running at IFCA provider. The same applies to the OpenStack2 instance in IFCA and the only OpenStack instance at INFN (in this case, the group would be INFN instead of IFCA).

The Mesos probe will do the same but given that there's only one Mesos cluster in IFCA it will create (if it doesn't exist) a group IFCA and a host with name s1 to send its metrics.

Assets 8
Loading