custom field in locust report

[stanislawskwark]

Is your feature request related to a problem? Please describe.

It would be helpful to have possibility to add custom fields to locust report

Describe the solution you'd like

I tried to show more or less what I mean on image:

so X would be a custom field and v1 v2 v3 some values. values of x field could be also accessible from code

Describe alternatives you've considered

Using custom separator like "|" in name works as a workaroud (i.e. "/blog|v2") but it's not very elegant

[cyberw]

Yes, this would be nice.

I have been thinking about adding a tags parameter to requests, which kind of relates to this. Tags could be general (like in your example), or more unique (like customer id).

The more difficult part (although maybe not that difficult) would be how this should be aggregated. You'd need to be able to select what tags should be considered when aggregating (probably in code), to control how requests are aggregated on workers, forwarded to the master and lastly displayed in the UI (in my example version is something that we'd want to aggregate, but customer id is probably not). If we want to do it "right", we should probably change "type" (post, get, etc) into a tag.

Tags should of course be passed to the request_success/failure methods. While we are at it, I think we should also pass the User instance on which they are called, and (as suggested in #1413) the full request/response object.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[cyberw]

This was partially addressed in #1750. Somebody could add aggregation and gui support.

[github-actions]

This issue was closed because it has been stalled for 10 days with no activity. This does not necessarily mean that the issue is bad, but it most likely means that nobody is willing to take the time to fix it. If you have found Locust useful, then consider contributing a fix yourself!