Bug 1929346

Summary: [cee/sd][RFE][RGW] Add operation (GET, PUT, DELETE, ...) counters/trackers in RadosGW per bucket and users
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Tomas Petr <tpetr>
Component: RGWAssignee: Ali Maredia <amaredia>
Status: ASSIGNED --- QA Contact: Madhavi Kasturi <mkasturi>
Severity: low Docs Contact:
Priority: medium    
Version: 4.2CC: amaredia, cbodley, ceph-eng-bugs, dparkes, kbader, mbenjamin, mhackett, nravinas, smykhail, swachira
Target Milestone: ---Keywords: FutureFeature
Target Release: 7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Petr 2021-02-16 17:28:46 UTC
Description of problem:
Add counters for client operations per users and buckets to be able monitor it via dashboard. 

To have RadosGW able store this information in counters/trackers and share this information with prometheus in order to be able to display it in the Ceph dashboard (a similar RFE will be opened to display this information).

What we would like to see is:
	-User: john-doe
		-Total number of operations.
		-Number of GET operations.
		-Number of PUT operations.
		-Number of DELETE operations.
		-If we can have this information per S3 path would be perfect as we might see what our users are doing:
			-Are they reading again and again a single file?
			-Are they overwriting again and again a single file?
	-Bucket: my-bucket
		-Total number of operations and the different users accessing the bucket.
		-Number of GET operations and the different users accessing the bucket.
		-Number of PUT operations and the different users accessing the bucket.
		-Number of DELETE operations and the different users accessing the bucket.
		-If we can have this information per S3 path would be perfect as we might see what our users are doing:
			-Are they reading again and again a single file?
			-Are they overwriting again and again a single file?


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Tomas Petr 2021-02-16 17:59:32 UTC
for reference BZ for Dashboard to display this data:
Bug 1929358 - [cee/sd][RFE][dashboard] Display operation (GET, PUT, DELETE, ...) counters/trackers from RadosGW in the Ceph dashboard
https://bugzilla.redhat.com/show_bug.cgi?id=1929358