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.

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 Monitoring Node.

elastic.yaml

Elastic checks gather metrics for Elasticsearch databases, such as the Log Database of SUSE OpenStack Cloud Monitoring. The configuration file must specify the URL for HTTP requests. If basic authentication is used, for example, elasticsearch-http-basic, the configuration file must also specify the user name and password for every instance that requires authentication.

The agent installer automatically creates the elastic.yaml configuration file in the /etc/monasca/agent/conf.d/ directory. If there is an Elasticsearch database instance installed on the machine where the agent is installed, you have to specify the configuration information in the elastic.yaml file after the installation.

Example configuration:

init_config: null
instances:
- dimensions:
    component: elasticsearch
    service: monitoring
  url: http://localhost:9200
  username: username
  password: password
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.

Crowbar configures HTTP checks for the following services on the Monitoring Node:

  • monasca-api

  • monasca-log-api

  • Kibana

  • Monasca Persister

http_metrics.yaml

HTTP metrics checks retrieve metrics from any URL that returns a JSON response. Based on a list of URLs, the agent can dispatch an HTTP request and parse the desired metrics from the JSON response.

Crowbar configures a HTTP metrics check for the monasca-persister service running on the Monitoring Node.

kafka_consumer.yaml

Kafka consumer checks gather metrics related to services consuming Kafka topics, such as the Persister or Notification Engine of SUSE OpenStack Cloud Monitoring.

Crowbar configures Kafka consumer checks for the Kafka service running on the Monitoring Node.

kibana.yaml

Kibana checks gather various statistics such as load, heap size and usage, and various request performance statistics from a Kibana server. The checks retrieve these statistics from Kibana's status endpoint.

Crowbar configures Kibana checks for the Kibana service running on the Monitoring Node.

mysql.yaml

MySQL checks gather various statistics such as buffer sizes and usage, reads/writes, network connections, etc. from a MySQL database server. MariaDB is also supported. The metrics are drawn from the server status variables of MySQL.

Crowbar configures the MySQL checks for the MariaDB database service running on the Monitoring Node.

ntp.yaml

Network Time Protocol checks monitor the time offset between an NTP server and the machine the agent is running on.

Crowbar configures the NTP check to monitor the offset between the Monitoring Node and the NTP server running on the Administration Server.

postfix.yaml

Postfix checks monitor the queue sizes (incoming, active, deferred) on a Postfix mail server.

Crowbar configures Postfix checks for the Postfix service running on the Monitoring Node.

zk.yaml

ZooKeeper checks gather metrics on nodes and connections covered by ZooKeeper, a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. The check parses the result of the ZooKeeper stat admin command.

Crowbar configures ZooKeeper checks for the ZooKeeper instance running on the Monitoring Node.

Print this page