# How elastic stack monitoring \> node \> advanced request rate works

**URL:** <https://discuss.elastic.co/t/how-elastic-stack-monitoring-node-advanced-request-rate-works/361282>\
**Category:** Logs\
**Tags:** elastic-stack-monitoring\
**Created:** [June 11, 2024, 4:59pm UTC](https://discuss.elastic.co/t/how-elastic-stack-monitoring-node-advanced-request-rate-works/361282 "2024-06-11T16:59:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kishorkumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kishorkumar/32/132930_2.png) [@kishorkumar](https://discuss.elastic.co/u/kishorkumar)\
**Post date:** [June 11, 2024, 4:59pm UTC](https://discuss.elastic.co/t/how-elastic-stack-monitoring-node-advanced-request-rate-works/361282/1 "2024-06-11T16:59:54Z")

</div>

I have tried to test the load with JMeter using the following configuration:

**Thread Group:**

**Threads (users)**: 100  
**Ramp-up time** : 1 second  
**Loop** : Infinity  
**Duration** : 300 seconds

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/7/475e858de5b37b398a943b2d019198d54cbefb0d.png)

Additionally, I have added to that Precise Throughput Timer :

**Add \> Timer \> Precise Throughput Timer** with batch default setting of 1.

So, the total requests (threads) I want are 30,000 in 300 seconds.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/f/4fc3593bf8ab0f51dccdd601ac322a5da23a0f2d.png)

**Summary Report:**

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/7/c72638c77400ec9f046786341ea93c8d122ceb26.png)

When I run this test on my server, I receive approximately **30,014** samples with a success rate and 0% error rate, but the GUI test shows a **99.5/sec** throughput in the JMeter result summary.

However, when I check the Elasticsearch monitoring, I see only 112 requests per 10-second interval, according to the hovering information. This makes me unclear about the actual number of requests per second being handled according to Elasticsearch monitoring.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/f/dfdac78f4d0cc0eee8eed6c88e65833c8e7fd841.png)

According to JMeter, it should show 6,000 requests per 10 seconds, but it's showing me a maximum of 99.5/sec, which is confusing. I would expect a per-second chart, but it's giving me a 10-second interval.

Can someone explain this discrepancy?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/f/dfdac78f4d0cc0eee8eed6c88e65833c8e7fd841.png)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/c/3ce3327a6ab40e55101041ec8ee004a34e17a455.png)

It should show 1,000/10s according to the JMeter calculation, but on my custom dashboard with a 10-second interval, I'm seeing a different result.

but when i applying same on my custom dashboard with 10s then i am having like \*10 .

As far as I know, these values are being calculated using counter\_rate, but it's also dividing by the interval, right?

#Elastic Stack #Elasticsearch #elastic-stack-monitoring #monitoring #Elasticsearch

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [June 13, 2024, 4:53pm UTC](https://discuss.elastic.co/t/how-elastic-stack-monitoring-node-advanced-request-rate-works/361282/2 "2024-06-13T16:53:56Z")

</div>

Hi @kishorkumar

I think you are reading the Elastic Monitoring Chart incorrectly.

> [@kishorkumar](#):
>
> However, when I check the Elasticsearch monitoring, I see only 112 requests per 10-second interval, according to the hovering information

The interval is 10 Second Granularity, but the Measurement is in Request / Sec

That pop up should really say

> Amount of search operations (per shard) per second

So that shows 112 Requests / sec. Change the Time picker, and you will see the granularity change, but the request rate should not.

Jmeter 99 req / sec  
Elastic 112 req / sec

In that case, the numbers are pretty aligned. The extra searches may be internal to Elastic or from another source.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [June 13, 2024, 5:03pm UTC](https://discuss.elastic.co/t/how-elastic-stack-monitoring-node-advanced-request-rate-works/361282/3 "2024-06-13T17:03:42Z")

</div>

Quick example (mine indexing not search) Notice the measurement is the same Request / sec

 ![Screenshot 2024-06-13 at 10.02.19 AM](https://us1.discourse-cdn.com/elastic/original/3X/e/f/efedb11fb128af492a999033b10db6a299bf7fee.jpeg)

 ![Screenshot 2024-06-13 at 10.02.09 AM](https://us1.discourse-cdn.com/elastic/original/3X/0/c/0c7bc70491eb777afd61eb1f9c8888911a9bc485.jpeg)

You can also look at the overview page... (this is not a good example for you but you can look there but that will account for All searches Accros All indices...

 ![Screenshot 2024-06-13 at 10.03.31 AM](https://us1.discourse-cdn.com/elastic/original/3X/1/0/107e12f238286dfa9341a15b4111a0c9260f5287.png)
