Description of problem: Customer wants to have exact same functions in mgr-resful-module which is present in deprecated ceph-rest-api. The following things related to rgw are not included in mgr-restful-module: rgw successful requests rgw failed requests rgw performance details (read/write iops, latency, throughput etc) rgw active connections rgw active thread number In mgr-module we can see the information about particular request using url => https://10.74.255.33:8003/request and https://10.74.255.33:8003/request/<id> , but we are unable to see the set of rgw failed request, rgw successful requests, rgw active thread number , connections and rgw performance details. The information about other arguments regarding rgw can be seen using url => https://10.74.255.33:8003/config/cluster But as we can see information related to monitor and osd separately using url => https://10.74.255.33:8003/mon and https://10.74.255.33:8003/osd respectively Version-Release number of selected component (if applicable): RHCS 3.2 How reproducible: Always Steps to Reproduce: 1. Enable and configure mgr restful module Actual results: Some rgw bits [ bits Mentioned below under Expected result ] are absent in mgr plugin. Expected results: rgw successful requests rgw failed requests rgw performance details (read/write iops, latency, throughput etc) rgw active connections rgw active thread number These should be included in mgr restful plugin. Additional info: I followed below doc to refer to mgr-module. https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/ceph_management_api/questions-and-answers Thanks Best regards, Servesha
Related: https://github.com/ceph/ceph/pull/27885
For 3.3, we could include the PR mentioned above if/when merged.
We need to use this bz to track the documentation effort for the ceph-mgr restful /request endpoint since I used the other bz to track the rgw bits back-port.
The upstream docs should be a starting point for documenting the /request endpoint: http://docs.ceph.com/docs/master/mgr/restful/#the-request-endpoint
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri
The guide has been updated on the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/ceph_management_api/index#how-can-i-execute-administrative-commands