OpenStack library for creating Guru Meditation Reports and other reports
Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.
Zuul a79a13b9a4 Merge "Add release notes links to doc index" 3 dni temu
doc Merge "Add release notes links to doc index" 3 dni temu
oslo_reports Stop to use the __future__ module. 3 dni temu
releasenotes Switch to newer openstackdocstheme and reno versions 2 tygodni temu
.coveragerc remove extraneous coverage omit instruction 4 lat temu
.gitignore Move doc related modules to doc/requirements.txt 11 miesięcy temu
.gitreview OpenDev Migration Patch 1 rok temu
.mailmap exported from oslo-incubator by 5 lat temu
.stestr.conf Switch to stestr 1 rok temu
.zuul.yaml Add Python3 victoria unit tests 1 miesiąc temu
CONTRIBUTING.rst Update the documentation link 2 lat temu
HACKING.rst Update hacking version 1 rok temu
LICENSE exported from oslo-incubator by 5 lat temu
README.rst Replace URLs with URLs 1 rok temu
lower-constraints.txt Merge "Remove the unused coding style modules" 1 tydzień temu
requirements.txt Updated from global requirements 2 lat temu
setup.cfg Remove translation sections from setup.cfg 3 tygodni temu remove outdated header 3 miesięcy temu
test-requirements.txt Update hacking for Python3 2 miesięcy temu
tox.ini Bump default tox env from py37 to py38 1 miesiąc temu


Team and repository tags



Latest Version


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