I'm using the Jenkins Performance Signature plugin with Dynatrace SAAS. It works as expected, but I'm having difficulty including Key Requests metrics in the performance report. In the spec file I have, for example:
where xxxxxxxxxxxxxxxx is the 16 character alphanumeric Service Method ID in the Dynatrace URL when I click on the appropriate key request.
However, when I run my Jenkins pipeline, in the console output I get:
at java.util.ArrayList.forEach(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
If I remove the keyRequest timeseries from the spec file Performance Signature handles the remaining definitions without problems.
I'm wondering whether it's because the keyRequest metrics seem to exist only in Dynatrace's Metrics v2 API, rather than the Timeseries v1 API. If so, does the definition in the spec file have to be altered before Performance Signature can process it correctly?
More broadly, if this doesn't work, are there any alternative approaches to include key request metrics in Performance Signature? The ideal, for me, would be a way of testing whether the 95th percentile timing for requests breaches a target (1 second, for example). I can obtain this information at a service level easily enough by using tags, but as far as I'm aware I can't tag individual requests (hence my attempted use of keyRequest timeseries.
Solved! Go to Solution.
Hi. The Performance Signature Plugin has a listing on the Dynatrace Hub with a link to a support email in case you have questions. While Raphael might watch this community portal I suggest you reach out to that support email as well. Here is the link to the hub listing: https://www.dynatrace.com/hub/detail/t-systems-jenkins/?query=performance+signature