[SERVER-76266] Separate out TTL deletions in $operationMetrics Created: 18/Apr/23  Updated: 06/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: storex-ranked
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Assigned Teams:
Storage Execution
Participants:

 Description   

Serverless users are sometimes surprised by their TTL deletions in their bills, and don't know where they come from. Today we don't isolate TTL deletions in the metrics which makes it hard to expose how much customers are paying for TTL deletions. We should provide a separate field for TTL specific metrics.



 Comments   
Comment by Irwin Dolobowsky [ 02/Aug/23 ]

Seems like a small but useful addition. Lets consider for an upcoming 7.X release.

Comment by Louis Williams [ 19/Apr/23 ]

Adding a `ttlDeletes` field to the set of $operationMetrics measurements should be straightforward for us, so we will wait until we have input on how we should schedule this.

Generated at Thu Feb 08 06:32:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.