----- Original Message -----
> Hi -
>
> > [...] I think the archive (especially with rsync) considerations
> > favour only updating/creating files for today's data each day. [...]
>
> By the way, as we don't provide any off-machine archiving facilities
> such as rsync, the default for archive collection need not be a
Hmm, not sure what you mean there? - rsync works fine, and people
use it for off-machine archiving all the time. Its not something
we need or should be providing, it just works. And it works as a
result of us not continually changing the historical archives.
> perfect match for that scenario. We don't need to especially cater to
> such elaborate configurations *in our defaults*.
"elaborate" is not a word I'd have chosen here - and "our defaults"
need to cater for as many people as possible, with a focus on the
needs of production systems. People need some kind of strategy
for storing data long-term - we don't tackle this side of things,
because it needs local knowledge (i.e. a system with very large
amounts of storage and associated issues - its often going to be
part of some backup or off-line access strategy for other data
that people have). In deployments I've been involved in, its not
ever been done on the production monitored machine(s) - where PCP
is running/logging - cos the storage requirements are not fixed
(as they are for pmmgr and pmlogger_daily - compressing/culling
after a certain time, sampling at fixed rates, and so on).
rsync works really well - I know of a number of production systems
using this model for long-term storage. Our default mechanism has
to work well with that class of use.
cheers.
--
Nathan
|