[HDDS-11511] OM deletion services should have consistent metrics

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: pull-request-available
• Assignee: Tejaskriya Madhan
• Reporter: Ethan Rose
• Created: 30/Sep/24 21:02
• Updated: 4 days ago 04: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 OM's directory deleting service, handling of files, empty dirs, and non-empty dirs may be tracked with different metrics.
  • 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 services may already have these metrics, but some specifically in the OM do not. This Jira should review all the services and fill in these metrics where they are missing.

Issue Links

• is required by: HDDS-11512 Create Grafana dashboard for tracking system wide deletion
• requires: HDDS-11510 All deletion services should support multiple threads
• split from: HDDS-11640 Deletion services in SCM, OM and DN should have consistent metrics
• links to: GitHub Pull Request #7377