Usage documentation
Short documentation on how to use this plugin.
Detailed documentation will follow soon.
Log into oVirt Webadmin Portal and select a data center, cluster, host, storage domain, virtual machine or pool.
A new subtab labeled "Monitoring Details" appears. In this new subtab you can see all service checks for this item with service output and status information.
On the right side detailed information and performance graphs (if PNP4nagios is installed) are provided.
Mappings is a feature which allows you to display virtual machines and hosts which have a different name in oVirt/RHEV and in Nagios/Icinga.
Furthermore you can display check results for datacenters, clusters, storage domains and vm pools using the mapping feature. The main issue here is, that the monitoring UI-plugin isn't aware of the host name and service names for these checks, so you have to specify them.
If hostnames are the same in oVirt/RHEV and Nagios/Icinga you can see the check results as described in section Usage. If not, create a mapping.
In this screenshot you can see a virtual machine which was not found in Icinga:
The reason for this is, that vm puppet-foreman is named puppet-foreman.lab.ovido.at in Icinga, so we add a mapping in /etc/monitoring-ui/mappings/vms.yml:
# Map vm names in oVirt/RHEV to host names in Icinga/Nagios statically
#
# Note: Use this only if hostnames differ in both systems!
#
"puppet-foreman": "ovido-compile-rhel6.server.ovido.at"
Note that this file must end with a newline!
You can use any filename for mappings you want, just make sure it ends with .yml.
If you use mod_fcgid don't forget to restart Apache, as all configuration files are cached when running the application with mod_fcgid.
Now you can see check results for this virtual machine:
For displaying results of datacenters, clusters, storagedomains and pools it's required to add the hostname and service names into a mapping file (See ovirt.yml as an example):
Datacenter mappings:
ovirt:
datacenters:
"ovido-local":
host: "ovido-rhevm.lab.ovido.at"
services:
- "RHEV DC Status Check"
- "RHEV DC Storagedomain Check - ovido-local"
- "RHEV DC Storagedomain Usage - ovido-local"
In this example the Icinga service names "RHEV DC Status Check", "RHEV DC Storagedomain Check - ovido-local" and "RHEV DC Storagedomain Usage - ovido-local" of Icinga hostname "ovido-rhevm.lab.ovido.at" are display in Monitoring Tab of datacenter "ovido-local".
See ovirt.yml for examples on how to display cluster, storagedomain and pool informations.
In next version (0.2) you'll be able to add these mappings via Monitoring UI-plugin GUI.