# is it possible to get the request details under request\_\<n\> in a Gatling report?

**URL:** <https://community.gatling.io/t/is-it-possible-to-get-the-request-details-under-request-n-in-a-gatling-report/4768>\
**Category:** Gatling (Open-Source)\
**Created:** [January 23, 2019, 9:20pm UTC](https://community.gatling.io/t/is-it-possible-to-get-the-request-details-under-request-n-in-a-gatling-report/4768 "2019-01-23T21:20:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Laure\_Pillet](https://avatars.discourse-cdn.com/v4/letter/l/ac8455/32.png) [@Laure\_Pillet](https://community.gatling.io/u/Laure_Pillet)\
**Post date:** [January 23, 2019, 9:20pm UTC](https://community.gatling.io/t/is-it-possible-to-get-the-request-details-under-request-n-in-a-gatling-report/4768/1 "2019-01-23T21:20:15Z")

</div>

i would like to get the “real” request under under request\_ in a Gatling report.

each time i am going back to the scala simulation to find out this information and i am wondering if there’s no better way?

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [January 23, 2019, 9:30pm UTC](https://community.gatling.io/t/is-it-possible-to-get-the-request-details-under-request-n-in-a-gatling-report/4768/2 "2019-01-23T21:30:14Z")

</div>

Renaming request\_ into something more meaningful?

---

<div class="post-metadata">

**Author:** ![Laure\_Pillet](https://avatars.discourse-cdn.com/v4/letter/l/ac8455/32.png) [@Laure\_Pillet](https://community.gatling.io/u/Laure_Pillet)\
**Post date:** [January 27, 2019, 5:47pm UTC](https://community.gatling.io/t/is-it-possible-to-get-the-request-details-under-request-n-in-a-gatling-report/4768/3 "2019-01-27T17:47:23Z")

</div>

Hello Stéphane,  
thanks for replying. the thing is that i am using a recorded scenario from har file.  
the generated report is great but when i need to check a specific request i want to know the details behind (eg uri and parameters).  
so each time i am going back to the scenario (scala source) and searching the corresponding request to get this information.  
i guess, there is a better way to do it and to have this information directly accessible from the report?