Was looking at using the EditorPerf test suite as a starting point for tracking stats and capturing traces for things like time to pie, and editor boot times for our team. We got errors about failing to resolve telemetry data for statistics. In EditorPerfStats.CSV you’re using FEngineLoop not FEngineLoop::Tick. Updating that fixed it for us, but raises the question if you’re using this for monitoring startup times/editor perf or if there is another recommendation.
We are aware and using the Automated Performance Testing plugin as well as the studio/editor telemetry.
Thanks we have fixed this locally for the next release.
Internally we make use of the csv but we also have a handful of other telemetry such as the StudioTelemetry plugin which can write timing regions to a data warehouse as part of the EditorPerf run which we then provide visualization and reports from (we do also maintain utrace files alongside the test runs which we use for more close inspections when higher level telemetry raises an alarm).