(In reply to Ionuț Goldan [:igoldan], Performance Sheriff from comment #1)
performance_data.PerformanceSignatureViewSet viewset suit well for this?
Number of alerts fields could be appended to the list of results.
I see this uses the old signature_hash, which we should also deprecate.
Yes, if you don't need the performance datum for each signature then this API should be fine. However, there's a method that the serializer for
PerformanceSummary API uses that would be worth moving into a separate class and using in the PerformanceSignature. It replaces the need for custom UI code (used by PerfSeriesModel.getSeriesList) that creates a name from the test suite and extra options. It'd be worth removing this UI code and letting the serializer perform this action. Doesn't need to be in this pr but I thought it'd be worth mentioning if you have the time and inclination (I can also file a bug). We then probably wouldn't need to return as many fields in the API (since some are only used in the UI to create the name).