This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.

The OpenStack Operator's Tasks

In order to use SUSE OpenStack Cloud Monitoring for monitoring your OpenStack services and servers, so-called agents must be installed and configured:

Monitoring

The Metrics agent is responsible for querying metrics and sending them to the Monitoring Service for further processing.

Metrics are self-describing data structures that are uniquely identified by a name and a set of dimensions. Each dimension consists of a key/value pair that allows for a flexible and concise description of the data to be monitored, for example, region, availability zone, service tier, or resource ID.

The Metrics Agent supports various types of metrics including the following:

Your individual agent configuration determines which metrics are available for monitoring your services and servers. For details on installing and configuring a Metrics Agent, refer to https://documentation.suse.com/soc/8/html/suse-openstack-cloud-crowbar-all/cha-depl-ostack.html#sec-depl-ostack-monasca.

As soon as an agent is available, you have access to the SUSE OpenStack Cloud Monitoring monitoring features. You work with a graphical user interface that is seamlessly integrated into your cloud infrastructure. Based on OpenStack Horizon, the user interface enables access to all monitoring functionality and the resulting large-scale monitoring data. A comfortable dashboard visualizes the health and status of your cloud resources.

SUSE OpenStack Cloud Monitoring provides functions for alarm and notification management. Template-based alarm definitions allow for monitoring a dynamically changing set of resources without the need for reconfiguration. While the number of underlying virtual machines is changing, for example, this ensures the efficient monitoring of scalable cloud services. Alarm definitions allow you to specify expressions that are evaluated based on the metrics data that is received. Alarm definitions can be combined to form compound alarms. Compound alarms allow you to track and process even more complex events. Notifications can be configured in order to inform SUSE OpenStack Cloud Monitoring users when an alarm is triggered.

For details on the monitoring functions, refer to Chapter 3, Monitoring.

Log Management

The Log Agent collects the log data from the services and servers and sends them to the Monitoring Service for further processing. For details on installing and configuring a Log Agent, refer to https://documentation.suse.com/soc/8/html/suse-openstack-cloud-crowbar-all/cha-depl-ostack.html#sec-depl-ostack-monasca.

SUSE OpenStack Cloud Monitoring stores the log data in a central database. This forms the basis for visualizing the log data for the SUSE OpenStack Cloud Monitoring users. Advanced data analysis and visualization of the log data is supported in a variety of charts, tables, and maps. Visualizations can easily be combined in dynamic dashboards that display changes to search queries in real time.

Based on OpenStack Horizon, the customizable dashboards are seamlessly integrated into your cloud infrastructure. They enable user access to all log management functionality.

GUI-based alarm and notification management is also supported for log data. Based on a template mechanism, you can configure alarms and notifications to monitor the number of critical log events over time. Compound alarms can be created to analyze more complex log events. This automation of log handling guarantees that you can identify problems in your their infrastructure early and find the root cause quickly.

For details on the log management functions, refer to Chapter 4, Log Management.