e954dd42e4
Collects technical requirements information from various chapters in the Architecture Design Guide and consolidates them into a single Functional technical requirements chapter. Change-Id: I9df8be788f941a58e9a9fa92f77905c7d18aaae4 Closes-bug: #1548154 Implements: blueprint archguide-mitaka-reorg
28 lines
957 B
ReStructuredText
28 lines
957 B
ReStructuredText
======================
|
|
Logging and monitoring
|
|
======================
|
|
|
|
OpenStack clouds require appropriate monitoring platforms to catch and
|
|
manage errors.
|
|
|
|
.. note::
|
|
|
|
We recommend leveraging existing monitoring systems to see if they
|
|
are able to effectively monitor an OpenStack environment.
|
|
|
|
Specific meters that are critically important to capture include:
|
|
|
|
* Image disk utilization
|
|
|
|
* Response time to the Compute API
|
|
|
|
Logging and monitoring does not significantly differ for a multi-site OpenStack
|
|
cloud. The tools described in the `Logging and monitoring chapter
|
|
<http://docs.openstack.org/openstack-ops/content/logging_monitoring.html>`__ of
|
|
the Operations Guide remain applicable. Logging and monitoring can be provided
|
|
on a per-site basis, and in a common centralized location.
|
|
|
|
When attempting to deploy logging and monitoring facilities to a centralized
|
|
location, care must be taken with the load placed on the inter-site networking
|
|
links.
|