Testing Non-HTTP Calls with Gatling: Extending Reporting Beyond HTTP Requests

I’m attempting to validate a non-HTTP request, specifically a custom function that queries data from a database. However, Gatling reports exclusively on HTTP calls. Is there a method within Gatling to assess non-HTTP requests and generate corresponding reports?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.