Switch to supported Perf usage in EVG

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: greenerbuild
    • None
    • None
    • Python Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      The perf.send command is no longer being maintained and will be decommissioned eventually. It has been replaced instead by a new end point that users are able to call from their evergreen files; this doc outlines a drop in solution that allows us to continue sending their performance data as is.

      The perf team aren't wrapping it in a new EVG command as that would require evergreen to maintain it, they are trying to decouple the submission and processing of performance data from evergreen's suite.

      The Evergreen patch UI will remain the same, both perf.send and this new end point land data in the same spot, the new endpoint is maintained by the perf team and and they have/will continue to add new features to it.

      Definition of done

      Incorporate the new perf send style

      Pitfalls

      None

            Assignee:
            Noah Stapp
            Reporter:
            Steve Silvester
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: