From d6f5d9c78d6e89a6bc421973ea62b1105fb39cfa Mon Sep 17 00:00:00 2001 From: Xingjian Zhang Date: Tue, 27 Sep 2022 11:22:47 +0800 Subject: [PATCH] doc: Fix OSprofiler docs Change-Id: I709a26a9fd17b1b9baa2fc9ad45af75a628ffb06 --- doc/source/admin/OSprofiler.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/source/admin/OSprofiler.rst b/doc/source/admin/OSprofiler.rst index bb73b00fb..30ca75f8f 100644 --- a/doc/source/admin/OSprofiler.rst +++ b/doc/source/admin/OSprofiler.rst @@ -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 used for data transfer. So Ceilometer only works when Messaging is enabled. + 2. ElasticSearch and MongoDB support both data collection and transfer. So they can be used standalone. @@ -79,12 +80,12 @@ So In this example, we should add the following config options:: [oslo_messaging_notifications] topics = notifications, profiler -Then restart Zaqar service +Then restart Zaqar service. 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: 1. OpenStack Client now supports OSprofiler by default. Only thing we need to