# Stats about requests/sec and response times
**URL:** https://discuss.elastic.co/t/stats-about-requests-sec-and-response-times/6128
**Category:** Elasticsearch
**Created:** [December 12, 2011, 2:55pm UTC](https://discuss.elastic.co/t/stats-about-requests-sec-and-response-times/6128 "2011-12-12T14:55:29Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Florian\_Munz](https://discuss.elastic.co/u/Florian_Munz)
#### Post date: [December 12, 2011, 2:55pm UTC](https://discuss.elastic.co/t/stats-about-requests-sec-and-response-times/6128/1 "2011-12-12T14:55:29Z")
Hi,
I'm looking for a way to graph requests/second and the response times
for these requests. Is there a way to do this using the stats API
calls or by configuring the logger?
Cheers,
Florian
---
### Author:  [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [December 12, 2011, 5:20pm UTC](https://discuss.elastic.co/t/stats-about-requests-sec-and-response-times/6128/2 "2011-12-12T17:20:03Z")
Hi,
as far as I can see, there are no stats for this. Same for speed
rates, such as documents per second (dps = indexing speed).
Some resource usage development and some document counters could be
derived from the existing stats and be graphed by rrd tools, though.
Server request/sec stats (or better cluster-wide stats across nodes)
are always half the truth, as they depend on the total workload, on
the number of connected clients, but do neglect the network latency
with the connected client. And, you may be in desire for stats per
client, per index, per app, whatever. There are some costs of tracing
and collecting those granularity of stats in ES itself, this could be
the reason why it's not there.
For my part, I measure those qps and dps stats at the search/indexing
remote client side, including the overhead of tcp network traffic over
port 9200 to and from the ES cluster. This is more close to the
"effective" qps/dps perceivable by the user.
Jörg
On Dec 12, 3:55 pm, Florian Munz [m...@podio.com](mailto:m...@podio.com) wrote:
> Hi,
>
> I'm looking for a way to graph requests/second and the response times
> for these requests. Is there a way to do this using the stats API
> calls or by configuring the logger?
>
> Cheers,
> Florian
---
### Author:  [@Karussell1](https://discuss.elastic.co/u/Karussell1)
#### Post date: [December 12, 2011, 8:26pm UTC](https://discuss.elastic.co/t/stats-about-requests-sec-and-response-times/6128/3 "2011-12-12T20:26:15Z")
There is a feature which logs slow queries (can be configured to log
all I think). But I also would do it myself...
Peter.
On 12 Dez., 15:55, Florian Munz [m...@podio.com](mailto:m...@podio.com) wrote:
> Hi,
>
> I'm looking for a way to graph requests/second and the response times
> for these requests. Is there a way to do this using the stats API
> calls or by configuring the logger?
>
> Cheers,
> Florian
---
### Author:  [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [December 12, 2011, 10:45pm UTC](https://discuss.elastic.co/t/stats-about-requests-sec-and-response-times/6128/4 "2011-12-12T22:45:02Z")
In both node stats and index stats you have search/indexing stats (and many
more), are they enough?
On Mon, Dec 12, 2011 at 10:26 PM, Karussell [tableyourtime@googlemail.com](mailto:tableyourtime@googlemail.com)wrote:
> There is a feature which logs slow queries (can be configured to log
> all I think). But I also would do it myself...
>
> Peter.
>
> On 12 Dez., 15:55, Florian Munz [m...@podio.com](mailto:m...@podio.com) wrote:
>
> > Hi,
> >
> > I'm looking for a way to graph requests/second and the response times
> > for these requests. Is there a way to do this using the stats API
> > calls or by configuring the logger?
> >
> > Cheers,
> > Florian
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 3:45am UTC](https://discuss.elastic.co/t/stats-about-requests-sec-and-response-times/6128/5 "2017-07-06T03:45:37Z")