Closed dn0 closed 7 years ago
The zoneid information in the monitoring context can be replaced by VM's uuid, e.g.:
item kstat.get[zone_vfs:{$ZONEID}::nread] -> kstat.get[zone_vfs::{HOST.NAME}:nread], where {HOST.NAME} == VM.uuid.
kstat.get[zone_vfs:{$ZONEID}::nread]
kstat.get[zone_vfs::{HOST.NAME}:nread]
Therefore we do not need the ZONEID macro in Zabbix and we do not need to update it every time the VM changes its status.
Also all monitoring templates using ZONEID need to be modified in https://github.com/erigones/esdc-factory/tree/master/ansible/roles/esdc-mon/files/templates
Code is ready in the v2.6 branch
dn0
commented
7 years ago dn0
commented
7 years ago
The zoneid information in the monitoring context can be replaced by VM's uuid, e.g.:
item
kstat.get[zone_vfs:{$ZONEID}::nread]->kstat.get[zone_vfs::{HOST.NAME}:nread], where {HOST.NAME} == VM.uuid.Therefore we do not need the ZONEID macro in Zabbix and we do not need to update it every time the VM changes its status.
Also all monitoring templates using ZONEID need to be modified in https://github.com/erigones/esdc-factory/tree/master/ansible/roles/esdc-mon/files/templates