I would suggest the following approach after looking at the source of Gatling and Gatling's Jenkins plugin:
- Extend gatling so that it produces a stats.json file in addition to global_stats.json. Right now the per-request stats are only available in the Javascript file js/stats.json.
- Extend the gatling Jenkins plugin so that it optionally parses the stats.json file and adds the per-request trends to the graphs. Users of the plugin should be able to configure for which request name they want to see the trend over time.
What do you think about this approach?
I would appreciate any pointers about how to do #1. I have a pretty good understanding about how I can do #2. But I am still lacking the details on what I would have to change in Gatling to produce the stats.json file.
Thanks,
Ingo