Hi,
I agree with the performance argument.
However, I think it would be a good thing to allow for including the number
of cores, e.g. having the possibility to return either average or sum
(average*ncore).
Cheers
On Mon, Nov 18, 2013 at 09:30:02AM +0100, Toni Moreno wrote:
> Hi Otis.
>
> I thin
Excerpts from Kaushal Shriyan's message of 2013-11-18 14:16:41 +0100:
> Hi,
>
> I have setup collectd on CentOS 6.4. Are there options to select time range
> for example 15/05/2013 to 23/05/2013? I mean to look for time series data
> in between this period
This really depends on what storage bac
Sounds good to me. Thanks for sharing!
Otis
--
Performance Monitoring * Log Analytics * Search Analytics
Solr & Elasticsearch Support * http://sematext.com/
On Mon, Nov 18, 2013 at 3:30 AM, Toni Moreno wrote:
> Hi Otis.
>
> I think this approach is much better in very big servers ( I usually
Hi,
I have setup collectd on CentOS 6.4. Are there options to select time range
for example 15/05/2013 to 23/05/2013? I mean to look for time series data
in between this period
Regards,
Kaushal
___
collectd mailing list
collectd@verplant.org
http://ma
Hi Otis.
I think this approach is much better in very big servers ( I usually work
in servers with up to 40 cores ) and is easier to parse a single line on
/proc/stats than calculate 40* 8 ( metrics/core) averages values.
It also makes to have simpler config files ( avoiding average plugin).
I w
