OpenStack library for creating Guru Meditation Reports and other reports
Go to file
2024-09-12 10:24:09 +00:00
doc Remove old excludes 2024-05-01 11:40:53 +09:00
oslo_reports Handle shell_completion option in test suite 2024-09-02 16:15:21 +02:00
releasenotes Update master for stable/2024.2 2024-09-05 16:01:59 +00:00
.coveragerc remove extraneous coverage omit instruction 2015-10-08 20:26:55 +00:00
.gitignore Move doc related modules to doc/requirements.txt 2019-07-06 00:52:54 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:41:50 +00:00
.mailmap exported from oslo-incubator by graduate.sh 2015-06-03 12:49:50 -04:00
.pre-commit-config.yaml pre-commit: Integrate bandit 2024-02-07 12:03:18 +09:00
.stestr.conf Switch to stestr 2018-07-03 16:05:38 +07:00
.zuul.yaml Update CI to use unversioned jobs template 2022-03-15 15:07:26 +00:00
CONTRIBUTING.rst Align contributing doc with oslo's policy 2020-05-04 18:28:54 +02:00
HACKING.rst Update hacking version 2019-02-17 11:16:48 +08:00
LICENSE exported from oslo-incubator by graduate.sh 2015-06-03 12:49:50 -04:00
README.rst Replace git.openstack.org URLs with opendev.org URLs 2019-04-23 05:34:29 +00:00
requirements.txt Remove old excludes 2024-05-01 11:40:53 +09:00
setup.cfg Make greenlet optional 2024-02-07 11:56:36 +09:00
setup.py remove outdated header 2020-02-11 18:50:21 +01:00
test-requirements.txt Remove old excludes 2024-05-01 11:40:53 +09:00
tox.ini Merge "pre-commit: Integrate bandit" 2024-02-08 13:39:33 +00:00

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.