• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

doc/source/H03-May-2022-192107

oslo.reports.egg-info/H03-May-2022-8770

oslo_reports/H01-Jul-2021-3,2092,034

releasenotes/H01-Jul-2021-407140

.coveragercH A D01-Jul-2021115 97

.mailmapH A D01-Jul-202189 43

.pre-commit-config.yamlH A D01-Jul-20211.3 KiB4037

.stestr.confH A D01-Jul-202153 43

.zuul.yamlH A D01-Jul-2021224 98

AUTHORSH A D01-Jul-20212.3 KiB6463

CONTRIBUTING.rstH A D01-Jul-2021856 2314

ChangeLogH A D01-Jul-20219.6 KiB430335

HACKING.rstH A D01-Jul-2021146 53

LICENSEH A D01-Jul-20219.9 KiB177149

PKG-INFOH A D01-Jul-20213.9 KiB8669

README.rstH A D01-Jul-20212.6 KiB6247

setup.cfgH A D01-Jul-2021912 3631

setup.pyH A D01-Jul-2021697 214

tox.iniH A D01-Jul-20211.5 KiB6050

README.rst

1========================
2Team and repository tags
3========================
4
5.. image:: https://governance.openstack.org/tc/badges/oslo.reports.svg
6    :target: https://governance.openstack.org/tc/reference/tags/index.html
7
8.. Change things from this point on
9
10===================================
11oslo.reports
12===================================
13
14.. image:: https://img.shields.io/pypi/v/oslo.reports.svg
15    :target: https://pypi.org/project/oslo.reports/
16    :alt: Latest Version
17
18.. image:: https://img.shields.io/pypi/dm/oslo.reports.svg
19    :target: https://pypi.org/project/oslo.reports/
20    :alt: Downloads
21
22When things go wrong in (production) deployments of OpenStack collecting debug
23data is a key first step in the process of triaging & ultimately resolving the
24problem. Projects like Nova has extensively used logging capabilities which
25produce a vast amount of data. This does not, however, enable an admin to
26obtain an accurate view on the current live state of the system. For example,
27what threads are running, what config parameters are in effect, and more.
28
29The project oslo.reports hosts a general purpose error report generation
30framework, known as the "guru meditation report"
31(cf http://en.wikipedia.org/wiki/Guru_Meditation) to address the issues
32described above.
33
34Models: These classes define structured data for a variety of interesting
35pieces of state. For example, stack traces, threads, config parameters,
36package version info, etc. They are capable of being serialized to XML / JSON
37or a plain text representation
38
39Generators: These classes are used to populate the model classes with the
40current runtime state of the system
41
42Views: views serialize models into say JSON, text or xml. There is also
43a predefined view that utilizes Jinja templating system.
44
45There will be a number of standard models / generators available for all
46OpenStack services
47
48StackTraceModel: a base class for any model which includes a stack trace
49ThreadModel: a class for information about a thread
50ExceptionModel: a class for information about a caught exception
51ConfigModel: a class for information about configuration file settings
52PackageModel: a class for information about vendor/product/version/package information
53
54Each OpenStack project will have the ability to register further generator
55classes to provide custom project specific data.
56
57* Free software: Apache license
58* Documentation: https://docs.openstack.org/oslo.reports/latest
59* Source: https://opendev.org/openstack/oslo.reports
60* Bugs: https://bugs.launchpad.net/oslo.reports
61* Release notes: https://docs.openstack.org/releasenotes/oslo.reports/
62