# Gatling shows spikes in response time but New Relic and Grafana don't

**URL:** <https://community.gatling.io/t/gatling-shows-spikes-in-response-time-but-new-relic-and-grafana-dont/9334>\
**Category:** Gatling (Open-Source)\
**Created:** [October 4, 2024, 5:49am UTC](https://community.gatling.io/t/gatling-shows-spikes-in-response-time-but-new-relic-and-grafana-dont/9334 "2024-10-04T05:49:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![trinp](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/trinp/32/1593_2.png) [@trinp](https://community.gatling.io/u/trinp)\
**Post date:** [October 4, 2024, 5:49am UTC](https://community.gatling.io/t/gatling-shows-spikes-in-response-time-but-new-relic-and-grafana-dont/9334/1 "2024-10-04T05:49:52Z")

</div>

**Gatling version** : 3.11.3 (must be up to date)  
**Gatling flavor** : java kotlin scala javascript typescript  
**Gatling build tool** : maven gradle sbt bundle npm

I read the [guidelines](https://community.gatling.io/t/welcome-in-the-gatling-community-our-code-of-conduct/6462) and [how to ask a question](https://community.gatling.io/t/how-to-ask-a-question/6538) topics.  
 I provided a [SSCCE](http://www.sscce.org/) (or at least, all information to help the community understand my topic)  
 I copied output I observe, and explain what I think should be.

Hi, I’m running concurrent 2000 Users test with a `forever` loop and some `throttle` to get my desire QPS, following closed workload model.  
When coming to investigation, I noticed that both Grafana graph and New Relic do not show any request or transactions that exceeded 1 seconds request, even memory and CPU was not overused showed on both monitoring tools, but Gatling shows around 30~60 requests that has response time that is higher than 1 second.  
**Note that I can only use 1 pod for references, I had double checked to ensure all pods statistics are the same and system was stable during the test time**

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/gatling2/original/2X/c/cd362b3fe6c37314cfd68c27f6feda0263367094.png)  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/gatling2/original/2X/8/884628f147a6252772a289f4626e0e35d5e4a662.png)  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/gatling2/original/2X/5/54f2e5132146044dfe4d9408f7e1c77e790fe5b0.png)

What could possibly happen during the test time that causing this difference ?

---

<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:** [October 4, 2024, 6:41am UTC](https://community.gatling.io/t/gatling-shows-spikes-in-response-time-but-new-relic-and-grafana-dont/9334/2 "2024-10-04T06:41:21Z")

</div>

Your APM is blind on lots of things, including:

- network latency between your clients/load generators and your edge server
- everything that happens in your edge server (here, your ingress), including DNS, TCP and TLS.

Note: Gatling Enterprise would give you additional metric to investigate this:

- number and duration of DNS resolutions,
- number and duration of TCP connect,
- state of TCP connections,
- number and duration of TLS handshakes.

---

<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:** [November 3, 2024, 6:41am UTC](https://community.gatling.io/t/gatling-shows-spikes-in-response-time-but-new-relic-and-grafana-dont/9334/3 "2024-11-03T06:41:35Z")

</div>

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