Use Case

As a... driver engineer
I want... to upload performance results with dsi's raw performance endpoint or onboard onto dsi

So that... our benchmark metadata is properly uploaded and our contexts are applied properly

This ticket came out of a query in #ask-devprod-performance that revealed that perf.send is no longer the preferred means of uploading benchmark results and silently ignores the metadata fields needed to get contexts to be correctly applied.

User Experience

• N/A

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• Will we be able to just use the raw performance endpoint?
• How much work will it be to onboard onto DSI?

Acceptance Criteria

Implementation Requirements

• Ensure that the benchmark results (including metadata) are correctly uploaded
• Verify that the tags are correctly applied
• Verify that contexts are correctly applied
  • https://performance-monitoring.corp.mongodb.com/context/name/Node%20BSON%20Alerting%20Context 
  • https://performance-monitoring.corp.mongodb.com/context/name/Node%20Driver%20Alerting%20Context
  • https://performance-monitoring.corp.mongodb.com/context/name/Node%20Driver%20Spec%20Benchmark%20Context
  •  

Testing Requirements

• TBD

Documentation Requirements

• TBD

Follow Up Requirements

• None