os/bluestore: update perf counter priorities#43405
Conversation
|
@ifed01 I see you added yourself as a reviewer-- let me know any suggestions you might have! I know Adam has a few that he hasn't put on the PR yet. We did discuss some better "nicks" for the counters, which I have updated. |
|
jenkins test signed |
|
Hey @neha-ojha, adding you to this PR in case you have a chance to review. No worries if you already have a lot on your plate though. We are simply looking to increase the priority of important BlueStore perf counters (and assign new nicks along the way) so that they can be fetched in Telemetry. |
neha-ojha
left a comment
There was a problem hiding this comment.
Overall looks fine to me, left some nits on the nick naming and we can probably squash the last commit into previous ones after addressing review comments
|
adding @epuertat, in case this affects the perf counters displayed by the dashboard in some way |
|
@ljflores FYI: there is my pending PR which introduces some more counters for BlueFS and arranges ones at BlueStore, e..g groups them in the source code, improves description etc. Just to make you aware about my suggestions how to [additionally] improve these things... |
|
jenkins test make check |
|
Yep! Sorry, missed to insert the link... |
ifed01
left a comment
There was a problem hiding this comment.
Cool! You might want to squash all the commits prior to merging though...
These perf counters do not show up in telemetry unless they are set to a "useful" priority or higher. Fetching these counters in telemetry may help to diagnose problems with RocksDB / BlueFS prefetching / insufficient cache sizes. Signed-off-by: Laura Flores <lflores@redhat.com>
c9811fe to
8790f04
Compare
epuertat
left a comment
There was a problem hiding this comment.
If the perf-counters' labels are not modified, I don't see any issues!
Perf counters can only be collected in Telemetry if their priorities are set to USEFUL or higher. Several BlueStore perf counters that were set to lower priorities may help to diagnose performance problems; as such, they have now been set to USEFUL.
Here is a comprehensive list of updated perf counters and reasoning behind including them in Telemetry:
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 tox