Ahh, yes - apologies for the typo, but glad we got it sorted! I'll convert the solving comment to an answer and fix the typo, so you can accept. ... View more

well, you can start with a table job_duration queue_time 'test_summary.duration' and check it your self. maybe they are in different units? Seconds vs minutes ? ... View more

That pretty much works perfectly thank you! Now my only remaining issue seems to be with test_summary.duration. If I end with this table build_number build_duration queue_time 'test_summary.duration' everything shows up fine except there are no values in the chart or table for test_summary. However if I remove the single quotes around it all those values will appear, but build_duration will disappear. I assume it has something to do with it being a string for some reason, but I don't know the workaround. ... View more

@cdgill you need to convert the duration to epoch and later change it to human readable format ... View more

job_duration doesn't include queue time, only includes test time. please note test run time is different with test_summary.duration when you run tests in parallel. If your jenkins support pipeline, I suggest you mark it with different stages https://jenkins.io/doc/pipeline/steps/pipeline-stage-step/ so the app will show a summary for each stage (stage run time and result) ... View more

hello @cdgill, try and run the search in verbose mode and look at the icons to the left of the fields: job_duration, queue_time and test_summary.duration as well as other fields that you eval. check if they are numerical "#" to the left or string "@" to the left. i assume one (or more) is a string and therefore can not be calculated with arithmetic functions. if thats the case, use: eval num_field = tonumber(string_field) or other way and then run your last calculation hope it solves it ... View more

search for builds don't have test cases index=jenkins_statistics "test_summary.total"=0 search for test case keyword index=jenkins "keyword" | `expand_testcase` ... View more