[HDDS-11640] Deletion services in SCM, OM and DN should have consistent metrics

• Type: Sub-task
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Labels: pull-request-available
• Assignee: Tejaskriya Madhan
• Reporter: Tejaskriya Madhan
• Created: 04/Nov/24 08:00
• Updated: 3 days ago 03:27

Description

All background deletion services in Ozone should publish the same set of metrics for each thread:

• Number of items handled in the last iteration
  • For services where one DB key is multiple blocks (key delete, SCM block transactions), a separate metric should exist for the number of blocks deleted in the iteration and the number of items processed.
• Time spent in the last iteration

Some of these metrics, This Jira should review all the services and fill in these metrics where they are missing.

Issue Links

• split to: HDDS-11511 OM deletion services should have consistent metrics
• links to: GitHub Pull Request #7426