[rabbitmq-discuss] Statistics gathering

[Flavio Pompermaier]

So, actually I have just to tune sample_retention_policies to keep and
aggregate statistics as long as I need!
Is there a way to reset those statistics (during development I think I will
make several tests in a day, but I think I'll keep stats for a day so I
need to reset those couters..)?
Moreover, I saw that detailed stats are available only for 10 seconds..do
you think it could be feasible to keep detailed data for an entire day or
does it occupy too much space on disk?
For example, I'd like to do something like:

{rabbitmq_management, [{sample_retention_policies,
                          [{global,   [{60, 5}, {3600, 60}, {86400, 1200}]},
                           {basic,    [{60, 5},{3600, 60}, {86400, 1200}]},
                           {detailed, [{10, 5},{3600, 60}, {86400, 1200}]}
                        ]},

What is not clear to me is which statistics provides each category..for
example, detailed what information does affects?
If i ask for /api/queues, will I receive more or less data if I had also
detailed infos?
Resolution defined in sample_retention_policies have different
granularities in order to perform cumulative stats faster and save disk,
right?
Because I could configure {basic, [{{86400, 5}]} but then I keep all 5-secs
samples for all the day and also compute aggregate stats will require to
pass all the samples..(correct me if I'm wrong).
Will HTTP api returns cumulative stats only? sample_age and sample_incr
parameters are useful only I want all samples, right?

Thanks for the support,
Flavio

On Thu, Jul 25, 2013 at 1:28 PM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 25/07/2013 10:45AM, Flavio Pompermaier wrote:
>
>> Yes, probably what I need is to correctly set those two parameters:
>>   - sample_retention_policies
>>   - collect_statistics_interval
>>
>
> It's not obvious to me that you want to change collect_statistics_interval.
>
>
>  Are they strictly related or they serve different purposes?
>>
>
> Well, they both have to do with statistics.
>
> collect_statistics_interval controls how frequently the various components
> in RabbitMQ emit stats events. It therefore controls the maximum possible
> resolution of stats you can get. The expectation is usually that you would
> leave it alone, but if you had a huge number of not-quite-idle queues /
> channels / connections you might want to increase it so that your server
> does not spend all its time emitting stats events.
>
> sample_retention_policies controls how long the management plugin holds
> onto statistics, and with what resolution. You might want to change this if
> you want it to hold statistics for longer.
>
>
>  How do I ask for global/basic/detailed cumulative stats (like those
>> collected by sample_retention_policies)?
>>
>
> Those names refer to different classes of stats you can get through the
> web UI / HTTP API. See http://www.rabbitmq.com/**management.html#sample-**
> retention <http://www.rabbitmq.com/management.html#sample-retention> for
> the mapping.
>
>
>  I think that I need those metrics..
>> With a small collect_statistics_interval (1 s) I have more precise data
>> but more overhead on the broker,
>>
>
> Yes.
>
>
>  but changing this parameters require also to change
>> sample_retention_policies right?
>>
>
> No.
>
>
>  Or it just run every 5 s and thus collects 5 samples (for default global
>> conf for example)..?
>>
>
> Not sure what you mean. If collect_statistics_interval is shorter than the
> shortest resolution in sample_retention_policies you'll be doing more work
> for no gain.
>
> Cheers, Simon
>
>
>> Best,
>> Flavio
>>
>> On Thu, Jul 25, 2013 at 11:28 AM, Simon MacMullen <simon at rabbitmq.com
>> <mailto:simon at rabbitmq.com>> wrote:
>>
>>     On 24/07/2013 6:17PM, Flavio Pompermaier wrote:
>>
>>         have you ever tried to set statistics interval to something like
>>         a week?
>>
>>
>>     I assume you mean sample_retention_policies (i.e. how long we hold
>>     stats for) rather than collect_statistics_interval (i.e. how
>>     frequently the broker should emit stats for the management plugin to
>>     collect).
>>
>>     No I haven't, although you should be fine as long as you reduce the
>>     resolution for data that's held for longer. Or put up with increased
>>     memory use.
>>
>>         Does it affect performance?
>>
>>
>>     Shouldn't do particularly.
>>
>>     Cheers, Simon
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130725/ca5f2d0c/attachment.htm>