How can I have Rate column to display RPS in HTML report?
I don’t see an option to add that with --summary-trend-stats
Hi @loadtester,
Welcome to the forum! 
I’d be happy to help with any question or doubt you have regarding k6, but it looks like you’re using a community-driven extension (it seems to me that k6-reporter isn’t really an extension that we officially maintain), so I think for this it’s better if you reach directly the maintainer through to the extension’s repository.
Thanks! 
Hi @loadtester did you review the new k6 web dashboard? It has Counters for http_reqs (count and rate) on the Summary tab. The data is the same as http_reqs in the console output.
I believe http_req_duration is a Trend type metric not a Counter.
Thank you, @richmarshall. I did look at the k6 dashboard but it does not have the required metrics and it only shows summary data (http_req_duration and group_duration). I’m looking to get count and rate (along with other key performance metrics min, max, avg, etc) by groups and by individual requests. Is there a way to get such data in k6 dashboard? Or any other report? Thank you.
For the standard console output, I have trend metrics (response timings) down the individual endpoint level, by tagging the URLs and defining scenario thresholds on those tags. The same should be possible with rate metrics. AFAIK these would appear automatically on the web dashboard in addition to the standard aggregated metrics. I’m not using the web dashboard daily yet, but I will try to get an example ready for you soon.
You can also get custom timing or rate counters in the output at the URL level by defining custom rate and trend metrics, these metrics all need to be defined during test init which should be straightforward if the distinct URLs are known in advance; probably in most situations the URLs are known.
Being able to tag the URLs as I describe above with distinct tags without much code also implies that URLs are known in advance but the thresholds for those URL tags are defined in the Scenario, which is also set during init. If the exact URLs were NOT known before the test started (for example, dynamically generated from an external source), code would be required to dynamically construct the tags or the trend metrics, AND create part of the scenario at run-time vs. a static/pre-existing scenario.
@loadtester try following this example with tags.