couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Shorin <kxe...@gmail.com>
Subject Re: How to make use of couchdb.request_time stats?
Date Mon, 25 Aug 2014 10:16:59 GMT
There is no of such. You should query this stat for specific sample
rate[1] and track stddev/mean for the specified time frame. The
current value isn't much helpful since it represents summary of all
request times.
See also: http://gws.github.io/munin-plugin-couchdb/guide-to-couchdb-monitoring.html#requests-time

[1]: http://docs.couchdb.org/en/latest/config/misc.html#stats/samples
--
,,,^..^,,,


On Mon, Aug 25, 2014 at 2:09 PM, Suraj Kumar <suraj.kumar@inmobi.com> wrote:
> Hi,
>
> The _stats API exposes a metric called request_time. It looks like this:
>
>    "couchdb" : {
>       [... snip ...]
>       "request_time" : {
>          "stddev" : 6205.853,
>          "min" : 1,
>          "max" : 550399.642857143,
>          "current" : 13495123.406,
>          "mean" : 1083.685,
>          "sum" : 13495123.406,
>          "description" : "length of a request inside CouchDB without
> MochiWeb"
>       }
>       [...]
>
> the 'current' value is a counter but the denominator is not available. What
> is a good denominator to use? Perhaps there is some other section of the
> _stats API which can be used?
>
> Thanks,
>
>   -Suraj
>
> --
> An Onion is the Onion skin and the Onion under the skin until the Onion
> Skin without any Onion underneath.
>
> --
> _____________________________________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.

Mime
View raw message