You are here

OpenStack Nova Server Monitoring

Requires Opsview Cloud or Opsview Monitor 6.4

This Host Template is part of the Openstack Monitoring Opspack

check_circle
Opsview Supported

Host Template: Cloud - OpenStack - Nova Server

Monitor the status of your OpenStack Servers/Instances.

This Host Template includes the following Service Checks:

Service Check Name Description Default Thresholds (Warning, Critical) UOM
OpenStack - Nova Server - CPU Usage The CPU usage of the server server_cpu_usage=70,90 %
OpenStack - Nova Server - Disk Bytes The rate of disk read/writes in bytes across all disks N/A bytes_per_minute
OpenStack - Nova Server - Disk Errors The rate of disk errors across all disks N/A per_minute
OpenStack - Nova Server - Disk Requests The rate of disk read/writes requests across all disks N/A per_minute
OpenStack - Nova Server - Memory Usage The current usage of the servers allocated memory server_memory_usage=70,90 %
OpenStack - Nova Server - Network In The rate of incoming packets received, dropped and lost N/A per_minute
OpenStack - Nova Server - Network Out The rate of outgoing packets sent, dropped and lost N/A per_minute
OpenStack - Nova Server - Status The current state of the server. Possible values are 'pending', 'paused', 'running', 'shutdown', 'crashed', 'suspended' N/A N/A

Usage Instructions

Step 1: Add this Host Template

Add the Cloud - OpenStack - Nova Server Host Template to your Opsview Cloud host. If the resource you're monitoring has no hostname or public IP, then open the Advanced settings pane and change Host Check Command to Always assumed to be UP.

For more information, refer to Opsview Knowledge Center - Adding Host Templates to Hosts.

Step 2: Add and configure variables required for this Host Template

The Service Checks in this Host Template use the following variables, and they will be added to your Opsview Cloud instance when you import the Opspack:

OPENSTACK_SERVICE_ENDPOINT

The Value is not used and therefore can be set to anything.

Parameter Position in Variable Name Description
--openstack-service-protocol Arg1 OpenStack Service Protocol The protocol (HTTP/HTTPS) that the OpenStack service is listening on.
--openstack-service-address Arg2 OpenStack Service Address The IP or hostname that the OpenStack service is listening on.
--openstack-service-port Arg3 OpenStack Service Port The port that the OpenStack service is listening on.
--openstack-service-version Arg4 OpenStack Service Version The version of the OpenStack service.

OPENSTACK_CREDENTIALS

The Value is not used and therefore can be set to anything.

Parameter Position in Variable Name Description
--username Arg1 OpenStack Username The username of your OpenStack monitoring credentials.
--password Arg2 OpenStack Password The password of your OpenStack monitoring credentials.
--domain Arg3 OpenStack Domain The OpenStack domain you wish to monitor.

OPENSTACK_KEYSTONE_ENDPOINT

The Value is not used and therefore can be set to anything.

Parameter Position in Variable Name Description
--openstack-keystone-service-protocol Arg1 OpenStack Keystone Protocol The protocol (HTTP/HTTPS) that the OpenStack keystone service is listening on.
--openstack-keystone-service-address Arg2 OpenStack Keystone Address The IP or hostname that the OpenStack keystone service is listening on.
--openstack-keystone-service-port Arg3 OpenStack Keystone Port The port that the OpenStack keystone service is listening on.

OPENSTACK_SERVER_NAME

Parameter Position in Variable Name Description
--server-name Value OpenStack Server Name The name of the OpenStack server / instance to monitor.

OPENSTACK_PROJECT

Parameter Position in Variable Name Description
--project Value OpenStack Project The OpenStack project you wish to monitor.

For more information, refer to Opsview Knowledge Center - Adding Variables to Hosts.

For mode-specific help, run the plugin with the -h -m <mode> flags. This will list the required and optional Variable Arguments for that mode. The appropriate mode for each Service Check is listed here:

Service Check Name Mode
OpenStack - Nova Server - CPU Usage OpenStack.Nova.Server.CPU
OpenStack - Nova Server - Disk Bytes OpenStack.Nova.Server.Disk.Bytes
OpenStack - Nova Server - Disk Errors OpenStack.Nova.Server.Disk.Errors
OpenStack - Nova Server - Disk Requests OpenStack.Nova.Server.Disk.Requests
OpenStack - Nova Server - Memory Usage OpenStack.Nova.Server.Memory
OpenStack - Nova Server - Network In OpenStack.Nova.Server.Network.RX
OpenStack - Nova Server - Network Out OpenStack.Nova.Server.Network.TX
OpenStack - Nova Server - Status OpenStack.Nova.Server.Status

SSL Certificates

Additionally, if ssl verification is required, you can use the following variable to pass in your SSL certificates for use when connecting to the service provider to gather metrics:

OPENSTACK_CERTIFICATES

The Value is not used and therefore can be set to anything. Override the arguments with your certificates.

Parameter Position in Variable Name Description
--ca-path Arg1 CA Certificate Path Path to the CA Certificate. Optional, only required if server verification is needed.
--client-cert Arg2 Client Certificate Path Path to the Client Certificate. Optional, only required if client verification is needed.
--client-key Arg3 Client Key Path Path to the Client Key. Optional, only required if client verification is needed.

Step 3: Apply changes and the system will now be monitored

OpenStack Nova Server Monitoring

Troubleshooting Permissions

The Opsview 'read' user requires 'GET' access to the following Nova endpoints with minimum scope of 'project':

  • /servers
  • /servers/{server_id}
  • /servers{server_id}/diagnostics

For more information regarding OpenStack Nova policies, refer to Nova configuration policy.