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.
Zuul 9da166ae7f Merge "Exclude tests from apidoc" 2 giorni fa
doc Exclude tests from apidoc 4 settimane fa
oslo_reports Update hacking version 9 mesi fa
releasenotes Update master for stable/train 2 mesi fa
.coveragerc remove extraneous coverage omit instruction 4 anni fa
.gitignore Move doc related modules to doc/requirements.txt 5 mesi fa
.gitreview OpenDev Migration Patch 7 mesi fa
.mailmap exported from oslo-incubator by graduate.sh 4 anni fa
.stestr.conf Switch to stestr 1 anno fa
.zuul.yaml Switch to Ussuri jobs 1 mese fa
CONTRIBUTING.rst Update the documentation link 2 anni fa
HACKING.rst Update hacking version 9 mesi fa
LICENSE exported from oslo-incubator by graduate.sh 4 anni fa
README.rst Replace git.openstack.org URLs with opendev.org URLs 7 mesi fa
babel.cfg exported from oslo-incubator by graduate.sh 4 anni fa
lower-constraints.txt tox: Keeping going with docs 1 mese fa
requirements.txt Updated from global requirements 1 anno fa
setup.cfg Add Python 3 Train unit tests 5 mesi fa
setup.py Updated from global requirements 2 anni fa
test-requirements.txt Move doc related modules to doc/requirements.txt 5 mesi fa
tox.ini tox: Keeping going with docs 1 mese fa

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.