This page covers how to add and configure the Red Hat Enterprise Virtualization (RHEV) connector using GroundWork Cloud Hub. The connection requires a unique set of parameters (e.g., endpoint, credentials). You will need your GroundWork server and virtual environment connector parameters handy.
WAS THIS PAGE HELPFUL?
To access Cloud Hub, log in to GroundWork Monitor as an Administrator and select (1) GroundWork Administration > GroundWork Cloud Hub.
The initial Cloud Hub screen is used to (2) Add new, or Start, Stop, Modify, obtain Status for, or Delete configured connectors.
The Start option enables a configured connector to begin the discovery and data collection process. If you decide you do not want to monitor a particular region, simply select Stop for the corresponding connector, the connectors configuration will be maintained for a subsequent start. Modify opens the Configuration page with a link to the Metrics screen. Status provides connection status information including error details. If a configured connector fails to connect, a connector-specific service will be updated to a Warning state, or Critical if you run out of retries (hosts will still become Unreachable and services Unknown if retries are exhausted). To stop and completely Delete a connection, see How to delete hosts. To keep a Cloud Hub connector configuration and temporarily suspend its monitoring, see Black List.
To (3) add a new connection click +Add corresponding to the Red Hat connector icon. You will need to create a new connection in this way for each region to be monitored.
Figure: Adding a connection
Next, in the configuration page (shown below) you will need to enter both the GroundWork server and remote server parameters. The data the GroundWork server receives comes from the remote virtualization server. The information is pulled from the API on a periodic basis based on the check interval that is set.
The (1) Groundwork Server is where Cloud Hub will store RHEV metrics. Often, this is the same server as where Cloud Hub is running. However, Cloud Hub can also be run in a distributed environment, on its own node in a GroundWork cluster. Here we enter the GroundWork server parameters, each described in the first table below.
Next enter values for the remote (2) RHEV Server, shown below and described in the second table.
Validate both server configurations by selecting the (3) Test button which will check if the connections are accessible with the given credentials. A dialog will be displayed with either a success message or, if the server cannot be contacted, an error message will be displayed with information describing why the connection failed.
(4) Views are optional features of RHEV. These features are the core components or services managed by RHEV. Views include Hypervisor View, Storage View, Network View, Resource Pool. Each of these services has their own rich set of metrics. By default, all services are selected. If checked, service will be monitored. RHEV also provides Cluster and Host metrics which can be optionally collected. If there are one or more clusters or hosts in the system, they will be automatically detected and collected. If you were collecting metrics for a service, and then unchecked that RHEV service, the existing hosts and metrics stored in the GroundWork server will be deleted.
And after the remote server parameters have been entered and verified, click (5) Save to save and write the entries to an XML file in the GroundWork server /usr/local/groundwork/config/cloudhub directory. The Cloud Hub connector is assigned an agent ID and that in turn becomes a record locator in Foundation when you begin monitoring. After the credentials have been validated click Next to start customizing metrics for this connection.
Figure: RHEV connector
Table: GroundWork server values
|GroundWork Server Version|| Indicates the minimum GroundWork Monitor version needed. In other words, a version below the indicated value is incompatible.
|Display Name||This is the configuration’s name displayed in the list of Cloud Hub connectors on the Cloud Hub home page.|
|GroundWork Server Name||The host name or IP address where a Groundwork server is running. A port number should not be entered here. If Groundwork is running on the same server, you can enter localhost.|
|Is SSL enabled on GroundWork Server?||Check this box if the GroundWork server is provisioned with a secure HTTPS transport.|
|GroundWork Web Services Username|| This is the provisioned user name granted API access on the GroundWork server.
|GroundWork Web Services Password|| The corresponding API Token (password) for the given Username on the GroundWork server, see GroundWork Administration > GroundWork License > Webservices API Account Info Token (encrypted).
|Merge hosts on GroundWork Server?||If checked, this option combines all metrics of same named hosts under one host. For example, if there is a Nagios configured host named demo1 and a Cloud Hub discovered host named demo1, the services for both configured and discovered hosts will be combined under the hostname demo1 (case-sensitive).|
Table: RHEV server values
|Is SSL enabled on RHEV Server?||Check this box if the RHEV server is configured for secure HTTPS.|
|RHEV-M Server||This is the name of the RHEV-M server and the domain name, e.g., rhev-m-server.yourdomain.com|
|RHEV-M entry-point||e.g., api|
|RHEV-M Login Name||The provisioned Username granted API access on the RHEV server.|
|RHEV-M Password||The corresponding Password for the given Username on the RHEV server.|
|RHEV-M Realm||RHEV-M realm is assigned when setting up the RHEV-M server. By default it is internal.|
|Certificate Store Path and Passcode||e.g., /usr/local/groundwork/java/jre/lib/security/cacerts|
|Check Interval (in mins)||This is the polling interval for collecting monitoring data from the virtual instance and sending it to the GroundWork server. The value is in minutes.|
|Sync Interval (in mins)|| This is the polling interval for collecting monitoring data from the virtual instance and sending it to the GroundWork server. The value is in minutes.
|Connection Retries (-1 infinite)|| This entry is the number of retries for the connection and sets a limit on how many attempts are made after a failure. If you set this to -1 the retrying goes on forever. The number set indicates how many connections are attempted before the connection is left inactive (until you restart it).
The metrics page is where you customize the lists of metrics being gathered for a connection. Out of the box, a complete list of metrics is provided for clusters, hosts, and RHEV services. Indicating a -1 for threshold fields will disable threshold triggers. A metric is considered inactive if it is not monitored.
Figure: RHEV metrics
Table: RHEV profile attribute options
|Attribute||The name of the service attribute (the metric name reported by the virtualization server).|
|Monitored||When on (checked) the service will be monitored.|
|Graphed||When on (checked) the service will be graphed.|
|Warning and Critical Thresholds||These values control the triggering of alerts. A Warning number larger than the Critical value will cause Cloud Hub to detect the metric as a trigger. Choosing a -1 in a threshold box will disable triggering on that alert.|
|Service Name||Cloud Hub automatically creates service names based on the metric name gathered from a virtualization server. The Service Name option adds the ability to report the polled metrics under a unique name that is set by the Administrator. Leaving the Service Name field blank defaults to the metric name reported by the virtualization server.|
|Description||A description of the service attribute.|