![liu-sheng](/assets/img/avatar_default.png)
This commit integrates functionality from the `openstack.common.report` module into Ceilometer. This enables Ceilometer services to receive SIGUSR1 and print a Guru Meditation Report to stderr or file. The required modules were added to 'openstack-common.conf' as well. Change-Id: Ic59c08a610dff7140f14304a60f1c3297d190239 Implements: blueprint guru-meditation-report
3.0 KiB
Guru Meditation Reports
Ceilometer contains a mechanism whereby developers and system administrators can generate a report about the state of a running Ceilometer executable. This report is called a Guru Meditation Report (GMR for short).
Generating a GMR
A GMR can be generated by sending the USR1 signal to any Ceilometer process with support (see below). The GMR will then be outputted standard error for that particular process.
For example, suppose that ceilometer-polling
has process
id 8675
, and was run with
2>/var/log/ceilometer/ceilometer-polling.log
. Then,
kill -USR1 8675
will trigger the Guru Meditation report to
be printed to
/var/log/ceilometer/ceilometer-polling.log
.
Structure of a GMR
The GMR is designed to be extensible; any particular executable may add its own sections. However, the base GMR consists of several sections:
- Package
-
Shows information about the package to which this process belongs, including version information
- Threads
-
Shows stack traces and thread ids for each of the threads within this process
- Green Threads
-
Shows stack traces for each of the green threads within this process (green threads don't have thread ids)
- Configuration
-
Lists all the configuration options currently accessible via the CONF object for the current process
Adding Support for GMRs to New Executables
Adding support for a GMR to a given executable is fairly easy.
First import the module (currently residing in oslo-incubator), as well as the Ceilometer version module:
from oslo_reports import guru_meditation_report as gmr
from ceilometer import version
Then, register any additional sections (optional):
'Some Special Section',
TextGuruMeditation.register_section( some_section_generator)
Finally (under main), before running the "main loop" of the
executable (usually service.server(server)
or something
similar), register the GMR hook:
TextGuruMeditation.setup_autorun(version)
Extending the GMR
As mentioned above, additional sections can be added to the GMR for a particular executable. For more information, see the inline documentation about oslo.reports: oslo.reports