openstack/zaqar
Code Issues Proposed changes

doc: Fix OSprofiler docs

Browse Source 
Change-Id: I709a26a9fd17b1b9baa2fc9ad45af75a628ffb06
This commit is contained in:
Xingjian Zhang 2022-09-27 11:22:47 +08:00 committed by Takashi Kajinami
parent d8fb6adf49
commit d6f5d9c78d
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/admin/OSprofiler.rst
View File

@ -25,6 +25,7 @@ OSprofiler now supports some kind of backends, such as Ceilometer, ElasticSearch
.. note:: 1. Ceilometer is only used for data collection, and Messaging is only .. note:: 1. Ceilometer is only used for data collection, and Messaging is only
used for data transfer. So Ceilometer only works when Messaging is enabled. used for data transfer. So Ceilometer only works when Messaging is enabled.
2. ElasticSearch and MongoDB support both data collection and transfer. So 2. ElasticSearch and MongoDB support both data collection and transfer. So
they can be used standalone. they can be used standalone.
@ -79,12 +80,12 @@ So In this example, we should add the following config options::
[oslo_messaging_notifications] [oslo_messaging_notifications]
topics = notifications, profiler topics = notifications, profiler
Then restart Zaqar service Then restart Zaqar service.
Command Line Command Line
------------ ------------
we can use OpenStack Client to analyse the user request now. For example, if we We can use OpenStack Client to analyse the user request now. For example, if we
want to know the performance for "queue list", we can do like this: want to know the performance for "queue list", we can do like this:
1. OpenStack Client now supports OSprofiler by default. Only thing we need to 1. OpenStack Client now supports OSprofiler by default. Only thing we need to