rgw: change section name of rgw_op counters#54623
Conversation
doc/radosgw/metrics.rst
Outdated
|
|
||
| "rgw_op": [ | ||
| The counters in the ``rgw_op_global`` section reflect the totals of each op metric for a given Ceph Object Gateway. | ||
| The counters in the ``rgw_op_user`` and ``rgw_op_bucket`` sections are labeled counters of op metrics for a user or bucket respectively. |
There was a problem hiding this comment.
| The counters in the ``rgw_op_user`` and ``rgw_op_bucket`` sections are labeled counters of op metrics for a user or bucket respectively. | |
| The counters in the ``rgw_op_user`` and ``rgw_op_bucket`` sections are labelled counters of op metrics for a user or bucket respectively. |
There was a problem hiding this comment.
Looks like both spellings are correct, it's just a matter of British vs American English: https://www.grammarly.com/blog/labeled-labelled/
There was a problem hiding this comment.
@zdover23 do you have an opinion on this spelling?
There was a problem hiding this comment.
exactly, we should try to lean into one spelling dialect
There was a problem hiding this comment.
FWIW labelled looks wrong to me, and we've tended toward Murican English in the past for docs, so I vote to leave it as it is.
There was a problem hiding this comment.
Even though I live in the Commonwealth, I think that American English is in ascendancy. "labelled".
|
Following points came upon discussion with @cloudbehl. @cloudbehl please feel free to add anything I may have missed. |
I'll go ahead and make the labels lowercase. For the other two suggestions, it's sounds like you have an issue with the names of the perf counters within the RGW. In the example you gave I don't think it makes sense to change these perf counters internally just because the metrics sent to Prometheus has the word "bucket" twice. Do you have a better name for those perf counters? |
|
@alimaredia Thanks for making the change. The naming convention and the metrics, looks good. Related to the global metrics, do we want to call it global explicitly or can we just use the regular name |
i don't care for the 'global' part either - it only makes sense if you know there are per-bucket/per-user versions in contrast what do you think about the names |
606a48c to
a59d7d2
Compare
|
@cloudbehl @avanthakkar updated with name changes |
cloudbehl
left a comment
There was a problem hiding this comment.
LGTM, minor nits in docs for the name change.
doc/radosgw/metrics.rst
Outdated
| The sections are ``rgw_op_global``, ``rgw_op_user``, and ``rgw_op_bucket``. | ||
|
|
||
| "rgw_op": [ | ||
| The counters in the ``rgw_op_global`` section reflect the totals of each op metric for a given Ceph Object Gateway. |
There was a problem hiding this comment.
| The counters in the ``rgw_op_global`` section reflect the totals of each op metric for a given Ceph Object Gateway. | |
| The counters in the ``rgw_op`` section reflect the totals of each op metric for a given Ceph Object Gateway. |
doc/radosgw/metrics.rst
Outdated
|
|
||
| To view op metrics in the Ceph Object Gateway go to the ``rgw_op`` sections of the output of the ``counter dump`` command:: | ||
|
|
||
| "rgw_op_global": [ |
There was a problem hiding this comment.
| "rgw_op_global": [ | |
| "rgw_op": [ |
doc/radosgw/metrics.rst
Outdated
| The sections are ``rgw_op_global``, ``rgw_op_user``, and ``rgw_op_bucket``. | ||
|
|
||
| "rgw_op": [ | ||
| The counters in the ``rgw_op_global`` section reflect the totals of each op metric for a given Ceph Object Gateway. |
There was a problem hiding this comment.
| The counters in the ``rgw_op_global`` section reflect the totals of each op metric for a given Ceph Object Gateway. | |
| The counters in the ``rgw_op`` section reflect the totals of each op metric for a given Ceph Object Gateway. |
a59d7d2 to
02029cd
Compare
cloudbehl
left a comment
There was a problem hiding this comment.
The PR looks good to me.
|
jenkins test api |
|
@cbodley can I get approval on this PR? |
|
jenkins test api |
|
@avanthakkar @cloudbehl for reference could you add some of the reasoning behind the motivation for this PR that you saw when you were building dashboards? Specifically why each section should have a consistent number of labels instead of varying labels. |
Hi Ali, We have two major issues with that.
|
|
@cbodley anything left to do here you see? should I run this through the verify suite in teuthology? |
The rgw_op section of `counter dump/schema` becomes: - rgw_op_global for the global op counters - rgw_op_per_user for the user labeled counters - rgw_op_per_bucket for the bucket labeled counters Signed-off-by: Ali Maredia <amaredia@redhat.com>
Signed-off-by: Ali Maredia <amaredia@redhat.com>
02029cd to
6a0960b
Compare
|
@cbodley this branched passed a minimal teuthology run: https://pulpito.ceph.com/amaredia-2024-02-01_05:08:51-rgw:verify-wip-rgw-op-metrics-section-rename-distro-default-smithi/ Is this enough or should I do a bigger one? |
please run the full rgw suite |
|
@cbodley here is a larger run of the rgw suite: https://pulpito.ceph.com/amaredia-2024-02-03_20:08:31-rgw-wip-rgw-op-metrics-section-rename-distro-default-smithi/ |
The rgw_op section of
counter dump/schemabecomes:Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windowsjenkins test rook e2e