openstack/openstack-manuals
Code Issues Proposed changes
Files
cb24f9363542f4b6f43b5d56cd56fd9dba5059a2
openstack-manuals/doc/arch-design-draft/source/operator-requirements-logging-monitoring.rst
daz bc05b757da [arch-design-draft] Reorganise operators requirements chapter 
1. Split sections into separate files
2. Consolidate hardware content from the current guide
3. Consolidate software content from the current guide

Change-Id: I5edf204d88ea5622c656fe58699260e31fb9b7d3
Implements: blueprint arch-guide-mitaka-reorg
2016-01-18 15:09:13 +01:00

957 B
Raw Blame History

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