-
Type:
Task
-
Resolution: Done
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
Not Needed
-
None
-
Not Needed
-
None
-
None
-
None
-
None
-
None
-
None
Use Case
As a... driver engineer
I want... __ to set the created_at and completed_at fields of our benchmark results correctly
So that... we have an easier time searching for benchmark results
User Experience
- What is the desired/expected outcome for the user once this ticket is implemented?
- If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
Dependencies
- upstream and/or downstream requirements and timelines to bear in mind
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- Is there an opportunity for better cross-driver alignment or testing in this area?
- Is there an opportunity to improve existing documentation on this subject?
Acceptance Criteria
Implementation Requirements
- Ensure that the time a benchmark begins and concludes are correctly recorded and reported in the info field of the metrics that get written out
Testing Requirements
- Manually verify that the timestamps are set correctly as required by https://performance-monitoring-service-rest.server-tig.prod.corp.mongodb.com/docs#/Raw%20Perf%20Results/add_raw_data_raw_perf_results_post
Documentation Requirements
- None
Follow Up Requirements
- None