Hello,
We followed the Tech Art guide for automated perf testing, and have it up and running, but when running with horde it tries to use a “PerfReportServer”. The AutomatedPerfTestNode doesn’t mention anything about it being an internal only tool, but Gauntlet.ReportGenUtils.cs does say “Attempts to create the PerfReportServerImporter. This importer is currently internal to Epic and such this function will return null when not used internally.”
So my question is what is the expectations for licensees? We could change our horde jobs to produce local reports and upload/consume the data on some central server ourselves.
Is Epic planning on releasing the “PerfReportServer” or adding the ability to for horde to consume these artifacts and display it ?
We can add GenerateLocalReports and then have ExtraAutomatedPerformanceCommonArgs add -LocalReports if true, but I am not clear how to get these to show up as artifacts for the buildandtest job.
Hey there Devon,
We are not currently looking at releasing the PerfReportServer., but we are looking to provide native support for such a view in Horde sometime in 5.8(?). The current path forward is as you’ve suggested - gather the local reports and set aside for subsequent processing via your preferred method.
Kind regards,
Julian
Hey there Devon,
Apologies for the delay in response. That is the idiomatic way to do so, and what we do internally.
Julian
I didn’t spot it in the docs, but how do you specify which artifacts get surfaced in Horde? I see stuff saved in “Saved/Engine/Programs/AutomationTool/Saved” but not where the reports get generated is showing, but not the local reports.
The uses I see of the CreateArtifact node it seems more for things that were built (like PDBs, and binaries) not for logs/reports.
Ended up just using the create artifact node for surfacing them.