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

**URL:** <https://community.gatling.io/t/testing-non-http-calls-with-gatling-extending-reporting-beyond-http-requests/8841>\
**Category:** Gatling (Open-Source)\
**Tags:** gatling-academy\
**Created:** [March 27, 2024, 2:38pm UTC](https://community.gatling.io/t/testing-non-http-calls-with-gatling-extending-reporting-beyond-http-requests/8841 "2024-03-27T14:38:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CAutomation](https://avatars.discourse-cdn.com/v4/letter/c/ecccb3/32.png) [@CAutomation](https://community.gatling.io/u/CAutomation)\
**Post date:** [March 27, 2024, 2:38pm UTC](https://community.gatling.io/t/testing-non-http-calls-with-gatling-extending-reporting-beyond-http-requests/8841/1 "2024-03-27T14:38:14Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/gatling2/original/2X/b/b148e0742de35c6280726cabf3ecd3de2d320f63.png) [@system](https://community.gatling.io/u/system)\
**Post date:** [April 26, 2024, 2:38pm UTC](https://community.gatling.io/t/testing-non-http-calls-with-gatling-extending-reporting-beyond-http-requests/8841/2 "2024-04-26T14:38:57Z")

</div>

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