Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE OpenStack Cloud Monitoring

A Supported Metrics

The sections below describe the metrics supported by SUSE OpenStack Cloud Monitoring:

  • Standard metrics for general monitoring of servers and networks.

  • Additional metrics for monitoring specific servers and services.

A.1 Standard Metrics

SUSE OpenStack Cloud Monitoring supports the following standard metrics for monitoring servers and networks. These metrics usually do not require specific settings. The metrics are grouped by metrics types. Each metrics type references a set of related metrics.

cpu.yaml

Metrics on CPU usage, e.g. the percentage of time the CPU is idle when no I/O requests are in progress, or the percentage of time the CPU is used at system level or user level.

disk.yaml

Metrics on disk space, e.g. the percentage of disk space that is used on a device, or the total amount of disk space aggregated across all the disks on a particular node.

load.yaml

Metrics on the average system load over different periods (e.g. 1 minute, 5 minutes, or 15 minutes).

memory.yaml

Metrics on memory usage, e.g. the number of megabytes of total memory or free memory, or the percentage of free swap memory.

network.yaml

Metrics on the network, e.g. the number of network bytes received or sent per second, or the number of network errors on incoming or outgoing network traffic per second.

These metrics are configured automatically on all machines and nodes that have the monasca-agent role assigned. This applies not only to network.yaml but also to all metrics covered in this chapter.

A.2 Additional Metrics

In addition to the standard metrics, SUSE OpenStack Cloud Monitoring automatically adds the following additional metrics to the monasca agent configuration on the OpenStack Controller.

http_check.yaml

HTTP endpoint checks perform up/down checks on HTTP endpoints. Based on a list of URLs, the agent sends an HTTP request and reports success or failure to the Monitoring Service.

The following barclamps will automatically create an HTTP check for the API services they deploy if the Monasca barclamp is active:

  • Barbican

  • Cinder

  • Glance

  • Heat

  • Keystone

  • Magnum

  • Manila

  • Neutron

  • Nova

  • Sahara

  • Swift

By default, the monitoring dashboard is configured to display the service status for the following services:

  • Cinder

  • Glance

  • Keystone

  • Neutron

  • Nova

  • Swift

The status visualization for additional services can be added manually.

postgres.yaml

Postgres checks gather various CRUD and system statistics for a database hosted by a PostgreSQL DBMS.

The following barclamps will automatically create Postgres checks for their service database if the Monasca barclamp is active:

  • Barbican

  • Cinder

  • Glance

  • Heat

  • Keystone

  • Magnum

  • Manila

  • Neutron

  • Nova

  • Sahara

Print this page