Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ap_verify
-
Labels:
-
Story Points:8
-
Epic Link:
-
Sprint:Alert Production F17 - 9, Alert Production F17 - 10
-
Team:Alert Production
Description
At the moment, we do not have a clear plan or framework for how we will make measurements of verify metrics, particularly those that are specific to a single Task's implementation details. Future development of ap_verify and feature requests for verify depend on how we intend to handle these metrics.
This ticket is for researching one or more designs for supporting metrics within the Task framework. The result shall be a tech note describing my understanding of the requirements for metrics usage, a summary of what verify currently supports, and specific proposals for how to incorporate metric measurements into Tasks and/or ap_verify. The note shall be sent for review to the stakeholders for verify, ap_verify, and pipe_base.
Per recommendation by John Swinbank, we're counting Chris Morrison's proofreading of DMTN-057's presentation and comprehensibility as the review.