My current project requires a HTML report to be generated by JMeter for publishing and subsequent work. It seems a logical approach to use the JMeter report dashboard, but I'm struggling to customise it. In particular I want to remove the apdex report as it's completely useless for what needs to be reported.
I thought it would be as simple as commenting out the relevant sections in index.html.fmkr, but if I comment out the section I actually lose all test results. In Dev tools I can see it causes the JS to fail (for example 'Cannot read properties of undefined (reading 'toLowerCase'). Similar things happen if I comment out other sections. Please bear in mind that I'm editing the files directly here using VS Code, I'm not using anything specific for fmkr files (whatever they may be).
My ultimate goal is to bring the response times over time graph to the front page in place of apdex, however I can see that's part of a different page so might be even more challenging.
For a specific question here, I would like to know how to remove the apdex section from the dashboard without losing the rest of the information on the page.
Add this line to <head
section of your index.html.fmkr
file
<meta http-equiv="refresh" content="0; url=content/pages/ResponseTimes.html">
and this will make Response Times Over Time chart the default page.
Alternatively you can change this:
<a class="navbar-brand" href="index.html">${reportTitle!"Apache JMeter Dashboard"}</a>
to this:
<a class="navbar-brand" href="content/pages/ResponseTimes.html">${reportTitle!"Apache JMeter Dashboard"}</a>
and this:
<a href="index.html"><i class="fa fa-dashboard fa-fw"></i> Dashboard</a>
to this:
<a href="content/pages/ResponseTimes.html"><i class="fa fa-dashboard fa-fw"></i> Dashboard</a>
JMeter HTML Reporting Dashboard is built on Apache FreeMarker® template engine, you might want to get familiarized with it if you want to do more heavy customizations.
Also if you're looking for interactive rich HTML reports you can consider running your JMeter test using Taurus tool as a wrapper, this is what you can get even while your test is running: