Error getting alarms on Zabbix instances

Bug #1733519 reported by Ifat Afek
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Vitrage
New
High
Unassigned

Bug Description

In order to get alarms from zabbix on a specific resource, the user should specify the resource type and name in zabbix_conf.yaml file, for example:

zabbix:
- zabbix_host: host1
  type: nova.host
  name: host-0-1
- zabbix_host: instance1
  type: nova.instance
  name: first-instance

When Zabbix datasource tries to relate the alarm to the resource, it uses the name of the resource as its *id*. For hosts, the name and the id are the same, so it doesn't matter. For instances (or other types) it doesn't work, so instead of raising the alarm on an existing instance, a new instance is created.

Workaround: write the id of the instance in the 'name' parameter, like:

- zabbix_host: instance1
  type: nova.instance
  name: <first-instance-UUID>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.