When running load tests via PerfSDK we sometimes need to troubleshoot strange long durations. This is a very hard task when single user tests via the UI showing good response times, but load tests via PerfSDK showing some peaks. If we would be able to use activity ids to troubleshoot via LCS, this would be very helpful.

To archive this goal, we would need to access the current ActivityId, to log this one e. g. with a custom processing. Another approach would be to use Application Insights, to log durations of single steps including the ActivityId of the step.