OpenStack library for creating Guru Meditation Reports and other reports
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
caoyuan 8a37087388 tox: Keeping going with docs 3 週之前
doc tox: Keeping going with docs 3 週之前
oslo_reports Update hacking version 9 月之前
releasenotes Update master for stable/train 1 月之前
.coveragerc remove extraneous coverage omit instruction 4 年之前
.gitignore Move doc related modules to doc/requirements.txt 4 月之前
.gitreview OpenDev Migration Patch 6 月之前
.mailmap exported from oslo-incubator by graduate.sh 4 年之前
.stestr.conf Switch to stestr 1 年之前
.zuul.yaml Add Python 3 Train unit tests 4 月之前
CONTRIBUTING.rst Update the documentation link 2 年之前
HACKING.rst Update hacking version 9 月之前
LICENSE exported from oslo-incubator by graduate.sh 4 年之前
README.rst Replace git.openstack.org URLs with opendev.org URLs 6 月之前
babel.cfg exported from oslo-incubator by graduate.sh 4 年之前
lower-constraints.txt tox: Keeping going with docs 3 週之前
requirements.txt Updated from global requirements 1 年之前
setup.cfg Add Python 3 Train unit tests 4 月之前
setup.py Updated from global requirements 2 年之前
test-requirements.txt Move doc related modules to doc/requirements.txt 4 月之前
tox.ini tox: Keeping going with docs 3 週之前

README.rst

Team and repository tags

image

oslo.reports

Latest Version

Downloads

When things go wrong in (production) deployments of OpenStack collecting debug data is a key first step in the process of triaging & ultimately resolving the problem. Projects like Nova has extensively used logging capabilities which produce a vast amount of data. This does not, however, enable an admin to obtain an accurate view on the current live state of the system. For example, what threads are running, what config parameters are in effect, and more.

The project oslo.reports hosts a general purpose error report generation framework, known as the "guru meditation report" (cf http://en.wikipedia.org/wiki/Guru_Meditation) to address the issues described above.

Models: These classes define structured data for a variety of interesting pieces of state. For example, stack traces, threads, config parameters, package version info, etc. They are capable of being serialized to XML / JSON or a plain text representation

Generators: These classes are used to populate the model classes with the current runtime state of the system

Views: views serialize models into say JSON, text or xml. There is also a predefined view that utilizes Jinja templating system.

There will be a number of standard models / generators available for all OpenStack services

StackTraceModel: a base class for any model which includes a stack trace ThreadModel: a class for information about a thread ExceptionModel: a class for information about a caught exception ConfigModel: a class for information about configuration file settings PackageModel: a class for information about vendor/product/version/package information

Each OpenStack project will have the ability to register further generator classes to provide custom project specific data.